AIIR verification and policy gates could report success without enforcing the control (fail-open)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Several 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. Found during an internal adversarial hardening review of AIIR (not a third-party audit). All paths are fixed in 1.7.0. Affected paths - A requiresigning 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. - A CI verification path could report success regardless of the underlying verification result. - A release-verification gate could advertise policy limits it did not actually enforce. - A signature-verification path could be silently skipped for certain input categories, exiting success without verifying. Impact A consumer…

Published by the source

28 Aug 2026, 19:20 UTC

Last modified by the source

28 Aug 2026, 19:20 UTC

Source last checked

26 Oct 2026, 13:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-73p9-6hrp-8qhr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-73p9-6hrp-8qhr

Advisory: AIIR verification and policy gates could report success without enforcing the control (fail-open)
IDs: GHSA-73p9-6hrp-8qhr
Record: https://patchnext.com/advisories/ghsa-73p9-6hrp-8qhr (revision 1, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: aiir 1.7.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI aiir: affected < 1.7.0; fixed in 1.7.0

## Suggested inspection (read-only)
- `python -m pip show aiir`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on aiir.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-73p9-6hrp-8qhr (GitHub-reviewed advisory GHSA-73p9-6hrp-8qhr lists affected ranges: PyPI aiir >=0 <1.7.0)

Commands are suggestions: review each one before running it.