# CVE-2026-130875: tac_plus-ng before commit d8493e0 Stack-Based Buffer Overflow via packet length checks


- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-j8j8-frcr-8f56, GHSA-v384-f7x8-f7c7

## What is CVE-2026-130875?

CVE-2026-130875 is a high-severity vulnerability in MarcJHuber tac_plus-ng, published on 17 Nov 2026. 

### Official description

tac_plus-ng before commit d8493e0 contains a stack-based buffer overflow vulnerability that allows clients holding the TACACS+ shared key to overflow a stack buffer due to an operator precedence error in author_pak_looks_bogus() and accounting_pak_looks_bogus(). Attackers can send packets whose argument-length table exceeds the payload, causing eval_args() to read past the packet and memcpy() oversized cmd values into cmdline, crashing the daemon or executing code.

Weakness: CWE-783 (Operator Precedence Logic Error)

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


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

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

## Is CVE-2026-130875 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130875 is a high-severity vulnerability in MarcJHuber tac_plus-ng, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130875 in the wild and no public exploit code.

Affected product: MarcJHuber tac_plus-ng. 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-130875/ (Markdown: https://insights.sbomify.com/CVE-2026-130875/index.md)
```

## Sources

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

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