Skip to content

v2.9.1

Latest

Choose a tag to compare

@GamehunterKaan GamehunterKaan released this 15 Nov 09:50
f2235c3

AutoPWN Suite v2.9.1

Functional changes

  • Breaking: AutoPWN Suite now needs Python 3.11.5 or newer; Python 3.10 is no longer supported. Python 3.10
    reached upstream end of life in October 2026, and the soupsieve releases that fix the advisories in the security
    notes require Python 3.11.5. On Python 3.10, pip and pipx keep resolving 2.9.0, the last release that supports
    it, and install.sh stops before it touches an existing installation. The Docker image and the standalone binaries
    bundle Python 3.13 and are unaffected. The Tests (...) and install smoke checks run on Python 3.11 instead of 3.10.
  • Update the locked soupsieve, the CSS selector library that beautifulsoup4 depends on, from 2.9 to 4.1
    (poetry.lock and the requirements-locked.txt exported from it), which the container image and the standalone
    binaries carry. The development-only backports tomli and exceptiongroup, which only Python 3.10 needed, leave
    the lock, and scripts/export_locked_requirements.py reads the lock with the standard library's tomllib only.
  • The macOS arm64 standalone binary is built on the macos-15 GitHub-hosted runner. GitHub retired the macos-14
    image on 2 November 2026, so the Standalone binaries / macos-arm64 job was cancelled at start, and the release
    workflow, whose push and signing jobs need every binary, would have stopped before publishing. The job and check
    names are unchanged. The runner does not set the binary's minimum macOS version: that comes from the pinned
    interpreter, the wheels chosen by fixed platform tags and the PyInstaller bootloader.
  • --apply-update verifies the release before moving the checkout. It downloads the release's
    release-manifest.json and its Sigstore bundle, checks the signature against this repository's release workflow,
    and refuses the update unless the manifest names the same commit the tag points at. --update-channel commit is
    unaffected, because main has no release manifest.
  • sigstore, which that check needs, is the optional update extra, because only a git checkout runs the check:
    pip, pipx and install.sh installations update from PyPI, and the Docker image and the standalone binaries do not
    update themselves. requirements.txt still lists it, so a checkout installed with pip install -r requirements.txt has it;
    a Poetry development environment gets it with poetry install --extras update. A checkout without it refuses
    --apply-update with the new update_extra_missing error, which names both commands, instead of reporting the
    release as unverified. scripts/export_locked_requirements.py leaves out the packages only an extra needs, so
    requirements-locked.txt, the Docker image and the standalone binaries carry none of the extra's packages
    (sigstore, tuf, pydantic, dnspython and the rest). The only change in that runtime set since 2.9.0 is
    typing-extensions 4.13.2 to 4.16.0, the version the shared lock resolves because sigstore-models needs it. The
    required test check installs the extra.
  • install.sh installs the package with its own declared dependencies by default instead of requirements.txt
    first, so its installations leave the update extra out as well. REQUIREMENTS_FILE still installs a
    dependency file before the package (requirements-locked.txt for hash-verified, lockfile-exact installs).

Security changes

  • soupsieve 4.1 fixes four denial-of-service advisories in compiling or matching CSS selectors:
    GHSA-mmhr-3c5m-f64f (CVE-2026-126190, high: polynomial time in the descendant combinator), GHSA-6655-6qjp-jx7x
    (CVE-2026-126191, high: exponential backtracking in selector compilation), GHSA-4j63-6c4x-wfg4 (CVE-2026-126192,
    medium: quadratic time for a general sibling combinator inside :has()) and GHSA-7g44-g9rc-x53w (CVE-2026-126193,
    medium: uncontrolled recursion on nested pseudo-classes). The pinned 2.9 is affected by all four, and no release
    that fixes the last three supports Python 3.10. AutoPWN Suite parses target HTML with Beautiful Soup but finds
    elements by tag name and never compiles a CSS selector, so there is no known impact on scans; the update keeps the
    locked dependencies free of known advisories, which the required Security policy check enforces. A pip or pipx
    install resolves its own soupsieve: upgrade it (pip install --upgrade soupsieve) if your environment kept an
    older one.
  • The macOS runner change has no security impact: the job keeps its read-only permissions, and the macOS binary is
    still built twice from the same hash-pinned inputs and must come out identical.
  • A moved or forged release tag no longer decides what --apply-update installs. Previously the tag's target was
    trusted as-is; now the attested build pins it, so pointing a tag at another commit makes the update refuse rather
    than install. Missing, unreadable, unsigned, or mismatched manifests are all refusals, and the updater still
    refuses entirely in offline mode.
  • sigstore, which verifies that signature, and its dependencies are the optional update extra. The Docker image,
    the standalone binaries and pip, pipx and install.sh installations of the package ship none of them, which keeps
    code they never run out of the published artifacts. A git checkout without the extra cannot verify a release, so
    it refuses the update rather than skip the check. The Security policy still scans the extra's packages, because it scans the whole poetry.lock.
    Installing the extra in the test job, which keeps the real Sigstore bundle parser under test, gives the job no
    new permission or secret, so it has no security impact.