A flaw was found in xdgmime. A heap-based buffer overflow can be triggered in _xdg_mime_magic_parse_magic_line() in the xdgmimemagic.c file on little-endian systems when an attacker-controlled MIME magic file in a user-writable XDG data location (e.g., in the $XDG_DATA_HOME/mime/magic path) is parsed by an application performing MIME type detection (e.g., via g_content_type_guess()). When performing byte-swap, incorrect pointer arithmetic on the write side causes an out-of-bounds write of 2 bytes, resulting in an application crash or memory corruption.
CVE-2026-16118
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-17. a secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(high)
- EG Risk
- 48(Track)EG Risk 48/100SSVC: Track
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 computedSeverity71% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 3.3%
- KEV
- Not listed
Published
July 17, 2026
Last Modified
July 22, 2026
Advisory Details (3)
Auto-updated Jul 17, 2026(#YWH-PGM9867-233) Heap Overflow on GLib through _xdg_mime_magic_parse_magic_line() in gio/xdgmime/xdgmimemagic.c via Incorrect Byte-Swap Pointer Arithmetic on MIME magic content in user-writable XDG data location (#41) · Issues · xdg / xdgmime · GitLab
https://gitlab.freedesktop.org/xdg/xdgmime/-/work_items/412501732 – (CVE-2026-16118) CVE-2026-16118 xdgmime: heap-based buffer overflow in _xdg_mime_magic_parse_magic_line() in xdgmimemagic.c
https://bugzilla.redhat.com/show_bug.cgi?id=2501732Vendor Advisories for CVE-2026-16118(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 14× 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.
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-23 00:12 UTCEG score recompute
- 2026-07-23 00:12 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-17 22:02 UTCEG score recompute
- 2026-07-17 22:02 UTCGHSA enrichment
- 2026-07-17 19:50 UTCEG score recompute
- 2026-07-17 19:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-122
Frequently asked(5)
What is CVE-2026-16118?
When was CVE-2026-16118 disclosed?
Is CVE-2026-16118 actively exploited?
What is the CVSS score of CVE-2026-16118?
How do I remediate CVE-2026-16118?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16118
Is Your Infrastructure Affected by CVE-2026-16118?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.