What is GHSA-73P9-6HRP-8QHR?

GHSA-73P9-6HRP-8QHR is a medium-severity security vulnerability in aiir (pip), affecting versions < 1.7.0. It is fixed in 1.7.0.

Which versions of aiir are affected by GHSA-73P9-6HRP-8QHR?

aiir (pip) versions < 1.7.0 is affected.

Is there a fix for GHSA-73P9-6HRP-8QHR?

Yes. GHSA-73P9-6HRP-8QHR is fixed in 1.7.0. Upgrade to this version or later.

Is GHSA-73P9-6HRP-8QHR exploitable, and should I be worried?

Whether GHSA-73P9-6HRP-8QHR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-73P9-6HRP-8QHR is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-73P9-6HRP-8QHR?

Upgrade aiir to 1.7.0 or later.

GHSA-73P9-6HRP-8QHR in aiir

Q: Which versions of aiir are affected by GHSA-73P9-6HRP-8QHR?

aiir (pip) versions < 1.7.0 is affected.

Q: Is there a fix for GHSA-73P9-6HRP-8QHR?

Yes. GHSA-73P9-6HRP-8QHR is fixed in 1.7.0. Upgrade to this version or later.

Q: Is GHSA-73P9-6HRP-8QHR exploitable, and should I be worried?

Whether GHSA-73P9-6HRP-8QHR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-73P9-6HRP-8QHR is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-73P9-6HRP-8QHR?

Upgrade aiir to 1.7.0 or later.

Summary

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

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 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.
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.

Workarounds

None 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.

Scope note

This advisory covers code present in released versions (< 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.

Impact

A 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.

Affected versions

aiir (< 1.7.0)

Security releases

aiir → 1.7.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Fixed in 1.7.0. Every affected path now fails closed, each with a regression test. Upgrade to aiir >= 1.7.0.

Frequently Asked Questions

What is GHSA-73P9-6HRP-8QHR? GHSA-73P9-6HRP-8QHR is a medium-severity security vulnerability in aiir (pip), affecting versions < 1.7.0. It is fixed in 1.7.0.
Which versions of aiir are affected by GHSA-73P9-6HRP-8QHR? aiir (pip) versions < 1.7.0 is affected.
Is there a fix for GHSA-73P9-6HRP-8QHR? Yes. GHSA-73P9-6HRP-8QHR is fixed in 1.7.0. Upgrade to this version or later.
Is GHSA-73P9-6HRP-8QHR exploitable, and should I be worried? Whether GHSA-73P9-6HRP-8QHR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-73P9-6HRP-8QHR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-73P9-6HRP-8QHR? Upgrade aiir to 1.7.0 or later.