# CVE-2026-125373: IETF Datatracker before 12.83.0 Cross-NomCom Authorization Bypass via Nomcom Views


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-767r-3gfx-x4wx

## What is CVE-2026-125373?

CVE-2026-125373 is a medium-severity vulnerability in ietf-tools datatracker, published on 9 Nov 2026. 

### Official description

IETF Datatracker before 12.83.0 contains an authorization bypass vulnerability that allows NomCom role holders to access other committees' records by supplying sequential primary keys. Attackers can abuse view_feedback_nominee, view_feedback_topic, view_feedback_unrelated and edit_nominee to view confidential nominee identities, reclassify feedback, and change nominee email addresses.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-125373 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125373 is a medium-severity vulnerability in ietf-tools datatracker, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125373 in the wild and no public exploit code.

Affected product: ietf-tools datatracker. 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-125373/ (Markdown: https://insights.sbomify.com/CVE-2026-125373/index.md)
```

## Sources

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

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