# CVE-2026-129129: AiSOC 12.1.0 before 23.3.0 Missing Authentication via Enrichment Console Proxy Routes


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-7cpc-qh93-pj89, GHSA-qf6m-hgwv-65f9

## What is CVE-2026-129129?

CVE-2026-129129 is a medium-severity vulnerability in beenuar AiSOC, published on 13 Nov 2026. 

### Official description

AiSOC 12.1.0 before 23.3.0 contains a missing authentication vulnerability that allows unauthenticated attackers to query the enrichment service through Next.js console rewrite routes. Attackers can send requests to /api/v1/enrichment/lookup or /api/v1/enrichment/bulk to retrieve threat-intelligence results and set force to true to consume commercial provider API quota.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

1 open source package ship an affected version, including beenuar/aisoc.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `beenuar/aisoc` | GitHub | `pkg:github/beenuar/aisoc` | From 12.1.0 | 23.3.0 |

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

Upgrade beenuar/aisoc to 23.3.0 or later.

## Is CVE-2026-129129 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129129 is a medium-severity vulnerability in beenuar AiSOC, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129129 in the wild and no public exploit code.

Affected packages and fixed versions:
- beenuar/aisoc (GitHub): affected from 12.1.0; fixed in 23.3.0

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-129129/ (Markdown: https://insights.sbomify.com/CVE-2026-129129/index.md)
```

## Sources

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

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