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

5.3 mediumEPSS 0.2%

Medium (5.3) in ietf-tools datatracker. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page

Severity
Ask an AI about this CVE
Affected
Versions
References
Your exposure

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.

Severity

CVSS 4.0

5.3 medium

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

CVSS 3.1

5.4 medium

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS: 0.2% estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC): Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE: CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10: A01:2025 Broken Access Control
Published: 2026-11-10 00:17 UTC
Modified: 2026-11-12 20:57 UTC
Assigned by: VulnCheck (CNA)
NVD analysis: Awaiting analysis
Record from: the NVD, synced 2026-11-12 21:27 UTC

Ask an AI about this CVE

ChatGPT Claude Google AI Mode

Show the prompt

Explain CVE-2026-125373 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125373?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125373?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125373 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-125373](https://cve.bz/cve/badge/CVE-2026-125373.svg)](https://cve.bz/cve/CVE-2026-125373)

HTML:

<a href="https://cve.bz/cve/CVE-2026-125373"><img src="https://cve.bz/cve/badge/CVE-2026-125373.svg" alt="CVE-2026-125373"></a>

Affected

ietf-tools:datatracker

Versions

From the CNA's record in the CVE List.

Product	Affected
ietf-tools datatracker	before 12.83.0

References

Check your stack JSON