cve.bz

CVE-2026-40489 editorconfig editorconfig-core-c: Stack-based Buffer Overflow

8.6 highEPSS 0.1%

High (8.6) in editorconfig editorconfig-core-c. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
editorconfig-core-c is an EditorConfig core library for use by plugins supporting EditorConfig parsing. Versions up to and including 0.12.10 have a stack-based buffer overflow in ec_glob() that allows an attacker to crash any application using libeditorconfig by providing a specially crafted directory structure and .editorconfig file. This is an incomplete fix for CVE-2023-0341. The pcre_str buffer was protected in 0.12.6 but the adjacent l_pattern[8194] stack buffer received no equivalent protection. On Ubuntu 24.04, FORTIFY_SOURCE converts the overflow to SIGABRT (DoS). Version 0.12.11 contains an updated fix.

Severity

CVSS 4.0

8.6 high
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
EPSS
0.1% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-04-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-121 Stack-based Buffer Overflow
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40489 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40489?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40489?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-40489 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
editorconfig-core-c< 0.12.11

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14editorconfig-coreno fix listedDEBIAN-CVE-2026-40489
Ubuntu24.04:LTSeditorconfig-core0.12.7-0.1ubuntu0.1UBUNTU-CVE-2026-40489
Ubuntu25.10editorconfig-core0.12.9+~0.17.1-1ubuntu2.1UBUNTU-CVE-2026-40489
Ubuntu26.04:LTSeditorconfig-core0.12.10+~0.17.1-3ubuntu0.1UBUNTU-CVE-2026-40489
UbuntuPro:16.04:LTSeditorconfig-core0.12.0-2ubuntu0.1~esm3UBUNTU-CVE-2026-40489 USN-8238-2
UbuntuPro:18.04:LTSeditorconfig-core0.12.1-1.1ubuntu0.18.04.1~esm3UBUNTU-CVE-2026-40489 USN-8238-2
UbuntuPro:20.04:LTSeditorconfig-core0.12.1-1.1+deb11u1ubuntu0.1~esm1UBUNTU-CVE-2026-40489 USN-8238-2
UbuntuPro:22.04:LTSeditorconfig-core0.12.5-2ubuntu0.1~esm3UBUNTU-CVE-2026-40489 USN-8238-2
SUSELinux Enterprise Module for Development Tools 15 SP7editorconfig-core-c0.12.6-150600.3.6.1SUSE-SU-2026:2731-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0editorconfig-core-c0.12.9-160000.3.1SUSE-SU-2026:22125-1
openSUSELeap 16.0editorconfig-core-c0.12.9-160000.3.1openSUSE-SU-2026:20966-1
openSUSETumbleweededitorconfig-core-c0.12.11-1.1openSUSE-SU-2026:10663-1
Alpinev3.24editorconfig0.12.11-r0ALPINE-CVE-2026-40489

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

References

Check your stackJSON