Medium, CVSS 6.9PyPIPublished
AIIR verification and policy gates could report success without enforcing the control (fail-open)
GHSA-73p9-6hrp-8qhr
- Affected
- PyPI aiir < 1.7.0
- Fixed in
- 1.7.0· Vendor fix available
- Issue
- 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…
Recommended action: Upgrade to 1.7.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.