CVE-2026-101014

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory published 2026-09-28. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this weekElevated
7.3EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.3Exploit: Elevated riskExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

A vulnerability was detected in Trusted Domain Project OpenDMARC up to 1.4.2. Affected by this vulnerability is the function opendmarc_util_cleanup in the library libopendmarc/opendmarc_util.c of the component DMARC Record Parser. Performing a manipulation results in off-by-one. The attack may be initiated remotely. The exploit is now public and may be used. The patch is named b3b1da9264bc80324094a27c71e7369bdedc62ae. To fix this issue, it is recommended to deploy a patch.

CVSS v3
7.3
EG Score
7.3HIGHhigh confidence
EG Risk
64
EG Risk 64/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

September 28, 2026

Advisory Details (4)

Auto-updated Sep 28, 2026
🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
github_commit

commit b3b1da9264bc (trusteddomainproject/OpenDMARC)

Fix landed in trusteddomainproject/OpenDMARC commit b3b1da9264bc — awaiting tagged release

https://github.com/trusteddomainproject/OpenDMARC/commit/b3b1da9264bc80324094a27c71e7369bdedc62ae
generic🟡 PoC Available

OpenDMARC off-by-one in opendmarc_util_cleanup() leaves an unterminated buffer, causing an out-of-bounds read in the DMARC record parser (OpenDMARC ≤ 1.4.2; latest version tested 2026-07-30)

https://weitongli.com/share/opendmarc-cleanup-off-by-one.html
github_pr

opendmarc_util_cleanup: fix off-by-one in buffer length guard

Fix merged in trusteddomainproject/OpenDMARC PR #344 on 2026-05-27 — awaiting tagged release

https://github.com/trusteddomainproject/OpenDMARC/pull/344
github_pr

Closed the gate for buffer overrun

Upstream fix in progress (PR #188 · trusteddomainproject/OpenDMARC, state=closed)

https://github.com/trusteddomainproject/OpenDMARC/pull/188

Vendor Advisories for CVE-2026-101014(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 35× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 01:02 UTCEG score recompute
  2. 2026-10-04 01:01 UTCGHSA enrichment
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-03 13:15 UTCGHSA enrichment
  5. 2026-10-03 01:29 UTCEG score recompute
  6. 2026-10-03 01:29 UTCGHSA enrichment
  7. 2026-10-02 13:42 UTCGHSA enrichment
  8. 2026-10-02 01:53 UTCEG score recompute
  9. 2026-10-02 01:53 UTCGHSA enrichment
  10. 2026-10-01 19:49 UTCEPSS rescore
  11. 2026-10-01 14:07 UTCGHSA enrichment
  12. 2026-10-01 02:21 UTCEG score recompute
  13. 2026-10-01 02:21 UTCGHSA enrichment
  14. 2026-09-30 15:02 UTCEPSS rescore
  15. 2026-09-30 14:36 UTCGHSA enrichment
  16. 2026-09-30 02:48 UTCEG score recompute
  17. 2026-09-30 02:48 UTCGHSA enrichment
  18. 2026-09-29 15:20 UTCEPSS rescore
  19. 2026-09-29 15:02 UTCGHSA enrichment
  20. 2026-09-29 03:16 UTCEG score recompute
  21. 2026-09-29 03:16 UTCGHSA enrichment
  22. 2026-09-28 15:28 UTCEG score recompute
  23. 2026-09-28 15:28 UTCGHSA enrichment
  24. 2026-09-28 13:50 UTCEPSS rescore
  25. 2026-09-28 13:29 UTCEG score recompute
Show 10 more
  1. 2026-09-28 13:29 UTCGHSA enrichment
  2. 2026-09-28 13:29 UTCNVD updateCVSS v4 → 5.5
  3. 2026-09-28 12:52 UTCEG score recompute
  4. 2026-09-28 12:52 UTCGHSA enrichment
  5. 2026-09-28 12:52 UTCMITRE cvelistV5CVSS v4 → 6.9
  6. 2026-09-28 09:32 UTCEG score recompute
  7. 2026-09-28 09:32 UTCGHSA enrichment
  8. 2026-09-28 09:31 UTCNVD updateCVSS v4 → 5.5
  9. 2026-09-28 08:42 UTCEG score recompute
  10. 2026-09-28 08:42 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-101014?
CVE-2026-101014 is a high vulnerability published on September 28, 2026. A vulnerability was detected in Trusted Domain Project OpenDMARC up to 1.4.2. Affected by this vulnerability is the function opendmarcutilcleanup in the library libopendmarc/opendmarc_util.c of the component DMARC Record Parser. Performing a manipulation results in off-by-one. The attack may be…
When was CVE-2026-101014 disclosed?
CVE-2026-101014 was first published on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-101014 actively exploited?
CVE-2026-101014 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101014?
CVE-2026-101014 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-101014?
An upstream fix for CVE-2026-101014 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-101014 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-101014

Explore →

Is Your Infrastructure Affected by CVE-2026-101014?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs