{"answers":{"affected":"2 open source packages ship an affected version, including aiir.","exploited":"There is no known exploitation of GHSA-73p9-6hrp-8qhr in the wild and no public exploit code.","fix":"Upgrade aiir to 1.7.0 or later.","what":"GHSA-73p9-6hrp-8qhr is a vulnerability in aiir, published on 28 Aug 2026."},"fix_prompt":"Check this codebase for GHSA-73p9-6hrp-8qhr and fix it if it is affected.\n\nWhat it is: GHSA-73p9-6hrp-8qhr is a vulnerability in aiir, published on 28 Aug 2026. \nExploitation: There is no known exploitation of GHSA-73p9-6hrp-8qhr in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- aiir (PyPI): affected all versions; fixed in 1.7.0\n- aiir (PyPI): affected all versions; fixed in 1.7.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-73p9-6hrp-8qhr/ (Markdown: https://insights.sbomify.com/GHSA-73p9-6hrp-8qhr/index.md)","id":"GHSA-73p9-6hrp-8qhr","markdown":"https://insights.sbomify.com/GHSA-73p9-6hrp-8qhr/index.md","name":"GHSA-73p9-6hrp-8qhr","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"unknown","non_default_config":false,"product_category":"Python verification library","requires_auth":"none","summary":"Attackers can bypass AIIR verification gates, causing unsigned or forged receipts to be incorrectly reported as verified, undermining trust in the verification process.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nSeveral of AIIR's verification and policy paths could return a success/\"verified\" result without actually enforcing the control they represent — they could **fail open** rather than fail closed. For a tool whose purpose is trustworthy verification, a consumer relying on these gates may have treated unverified or non-conforming input as verified.\n\nFound during an internal adversarial hardening review of AIIR (not a third-party audit). All paths are fixed in **1.7.0**.\n\n### Affected paths\n- A `require_signing` policy gate could be satisfied by a forgeable/empty field, so an unsigned or forged-bundle receipt could pass a \"signing required\" check without a valid signature.\n- A CI verification path could report `success` regardless of the underlying verification result.\n- A release-verification gate could advertise policy limits it did not actually enforce.\n- A signature-verification path could be silently skipped for certain input categories, exiting success without verifying.\n\n### Impact\nA consumer relying on these gates (e.g. `require_signing`, release/policy verification, or the CI check) to block unsigned, forged, or non-conforming receipts could have received a false \"verified\"/\"pass\". Exploitation requires reliance on the affected gate; it does not forge valid signatures, nor does it compromise content-addressing or correctly-signed receipts.\n\n### Patches\nFixed in **1.7.0**. Every affected path now fails closed, each with a regression test. Upgrade to `aiir \u003e= 1.7.0`.\n\n### Workarounds\nNone for earlier versions other than upgrading. Full cryptographic Sigstore verification (`pip install aiir[sign]`, `--verify-signature` with `--signer-identity`/`--signer-issuer`) provides defense in depth.\n\n### Scope note\nThis advisory covers code present in released versions (`\u003c 1.7.0`). Separately, an unreleased agent-receipt feature had pre-release forgery findings fixed before it shipped — those were never in a released version and are out of scope.","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"AIIR verification and policy gates could report success without enforcing the control (fail-open)","id":"GHSA-73p9-6hrp-8qhr","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":["1.7.0"],"introduced":["0"],"last_affected":[],"package":"aiir","purl":null,"source":"GHSA-73p9-6hrp-8qhr"},{"ecosystem":"PyPI","fixed":["1.7.0"],"introduced":["0"],"last_affected":[],"package":"aiir","purl":"pkg:pypi/aiir","source":"GHSA-73p9-6hrp-8qhr"}],"products":null,"published":"2026-08-28","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass AIIR verification gates, causing unsigned or forged receipts to be incorrectly reported as verified, undermining trust in the verification process.","url":"https://insights.sbomify.com/GHSA-73p9-6hrp-8qhr/"}