GHSA-73p9-6hrp-8qhr: Aiir AIIR Verification And Policy Gates Vulnerability

MODERATE
Share
CWE-636 CWE-347
Published
Advisory Summary

GHSA-73p9-6hrp-8qhr is a MODERATE aiir verification and policy gates vulnerability (CWE-636: Not Failing Securely ('Failing Open')) affecting Aiir libraries in the PyPI ecosystem. The issue involves aiir verification and policy gates could report success without enforcing the control (fail-open). Remediation is available by upgrading affected packages to version 1.7.0.

GHSA-73p9-6hrp-8qhr at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-73p9-6hrp-8qhr
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-636: Not Failing Securely ('Failing Open')
Affected Product Aiir
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix GHSA-73p9-6hrp-8qhr

To remediate this vulnerability, upgrade all affected Aiir dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

aiir fixed: 1.7.0 
pip install aiir>=1.7.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show aiir

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-73p9-6hrp-8qhr, inspect your installed packages using pip:

pip show aiir

Analyze the terminal output to locate any version of Aiir in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.7.0), your application is affected.

Note: The pip show aiir command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-636: Not Failing Securely ('Failing Open'), where when the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions. In Aiir, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 `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. ### 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. ### Patches Fixed in **1.7.0**. Every affected path now fails closed, each with a regression test. Upgrade to `aiir >= 1.7.0`. ### 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.

GHSA-73p9-6hrp-8qhr Affected Aiir Versions

1 component(s)
Fixed Versions:
1.7.0
Product / Package Ecosystem Affected Versions Fixed Version
aiir
pypi/aiir
PyPI
< 1.7.0
1.7.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/invariant-systems-ai/aiir/security/advisories/GHSA-73p9-6hrp-8qhr
Aiir Source Repository REPOSITORY
https://github.com/invariant-systems-ai/aiir

Frequently Asked Questions

What is GHSA-73p9-6hrp-8qhr?
GHSA-73p9-6hrp-8qhr is a security vulnerability in Aiir involving AIIR verification and policy gates could report success without enforcing the control (fail-open) under CWE-636: Not Failing Securely ('Failing Open').
Which Aiir versions are affected?
Affected versions include releases prior to 1.7.0 across affected packages: aiir.
What version fixes GHSA-73p9-6hrp-8qhr?
Upgrading to 1.7.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is aiir affected?
Yes, aiir is affected in releases prior to 1.7.0. Upgrade your dependency to 1.7.0 or later.
What CWE is associated with GHSA-73p9-6hrp-8qhr?
GHSA-73p9-6hrp-8qhr is classified under CWE-636: Not Failing Securely ('Failing Open') (When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions.).
How can I check PyPI dependencies for GHSA-73p9-6hrp-8qhr?
Run the dependency tree command: 'pip show aiir'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-73p9-6hrp-8qhr",
  "modified" : "2026-08-28T19:20:32Z",
  "published" : "2026-08-28T19:20:32Z",
  "aliases" : [ ],
  "summary" : "AIIR verification and policy gates could report success without enforcing the control (fail-open)",
  "details" : "### 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 >= 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 (`< 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.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "aiir"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.7.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/invariant-systems-ai/aiir/security/advisories/GHSA-73p9-6hrp-8qhr"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/invariant-systems-ai/aiir"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-347", "CWE-636" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-28T19:20:32Z",
    "nvd_published_at" : null
  }
}