# CVE-2026-105161: invariant-systems-ai aiir Policy Gate signature verification

> Attackers can bypass policy gate security controls due to improper cryptographic signature verification in the aiir library.

- **Severity:** Medium 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/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-7x65-vqw4-92q7

## What is CVE-2026-105161?

CVE-2026-105161 is a medium-severity vulnerability in invariant-systems-ai aiir, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw has been found in invariant-systems-ai aiir up to 1.7.0. The affected element is an unknown function of the component Policy Gate Handler. Executing a manipulation can lead to improper verification of cryptographic signature. The attack can be executed remotely. It is advisable to upgrade the affected component. The GitHub repository of this project is not available anymore. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-105161?


## How do I fix CVE-2026-105161?

No fix has been published for CVE-2026-105161 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105161 being exploited?

There is no known exploitation of CVE-2026-105161 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105161 and fix it if it is affected.

What it is: CVE-2026-105161 is a medium-severity vulnerability in invariant-systems-ai aiir, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105161 in the wild and no public exploit code.

Affected product: invariant-systems-ai aiir. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105161/ (Markdown: https://insights.sbomify.com/CVE-2026-105161/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105161
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105161
- OSV: https://osv.dev/vulnerability/CVE-2026-105161

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105161/
Summaries are generated and may contain mistakes; the official description above is the record.