CVE-2026-103680

LOWPre-NVD 3.13.1—
EchelonGraph scoreHIGH confidence

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-10-01. A secondary CVSS source baseline 3.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 3.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

A flaw was found in tnef. A heap-based buffer overflow can occur in the find_free_number() function when generating numbered backup suffixes for duplicate filenames. When numbered backups are enabled and file overwriting is disabled, an attacker can supply a specially crafted Transport Neutral Encapsulation Format (TNEF) file with an excessive number of colliding attachment filenames, causing the numeric counter to write past the allocated memory buffer. This issue may result in an application crash, leading to a Denial of Service (DoS), or potentially arbitrary code execution.

CVSS v3
3.1
EG Score
3.1LOWhigh confidence
EG Risk
14
EG Risk 14/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
Severity31% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (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

October 1, 2026

Last Modified

October 1, 2026

References (3)

Vendor Advisories for CVE-2026-103680(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
tnef1.4.18-3, 1.4.18-4, 1.4.18-5, 1.4.18-6
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
tnef1.4.18-4, 1.4.18-5, 1.4.18-6
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
tnef1.4.18-4, 1.4.18-5, 1.4.18-6
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 13× 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 23:21 UTCEPSS rescore
  2. 2026-10-04 16:03 UTCEG score recompute
  3. 2026-10-04 16:03 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-01 15:23 UTCEG score recompute
  6. 2026-10-01 15:23 UTCGHSA enrichment
  7. 2026-10-01 15:06 UTCEG score recompute
  8. 2026-10-01 15:06 UTCGHSA enrichment
  9. 2026-10-01 13:09 UTCEG score recompute
  10. 2026-10-01 13:09 UTCGHSA enrichment
  11. 2026-10-01 12:28 UTCEG score recompute
  12. 2026-10-01 11:48 UTCEG score recompute
  13. 2026-10-01 11:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-103680?
CVE-2026-103680 is a low vulnerability published on October 1, 2026. A flaw was found in tnef. A heap-based buffer overflow can occur in the findfreenumber() function when generating numbered backup suffixes for duplicate filenames. When numbered backups are enabled and file overwriting is disabled, an attacker can supply a specially crafted Transport Neutral…
When was CVE-2026-103680 disclosed?
CVE-2026-103680 was first published on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-103680 actively exploited?
CVE-2026-103680 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103680?
CVE-2026-103680 has a CVSS base score of 3.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-103680?
No fix for CVE-2026-103680 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-103680 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-103680

Explore →

Is Your Infrastructure Affected by CVE-2026-103680?

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

Book a Demo →Browse All CVEs