# CVE-2026-40489: editorconfig-core-c has incomplete fix for CVE-2023-0341


- **Severity:** High 8.6 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-40489, GHSA-97xg-vrcq-254h, OESA-2026-2258, OESA-2026-2259, OESA-2026-2260, SUSE-SU-2026:22125-1, SUSE-SU-2026:2731-1, UBUNTU-CVE-2026-40489, USN-8238-1, USN-8238-2, openSUSE-SU-2026:10663-1, openSUSE-SU-2026:20966-1

## What is CVE-2026-40489?

CVE-2026-40489 is a high-severity vulnerability in editorconfig-core-c, published on 18 Apr 2026. 

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-40489?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `editorconfig-core-c` | SUSE:Linux Enterprise Module for Development Tools 15 SP7 | All versions | 0.12.6-150600.3.6.1 |
| `editorconfig-core-c` | SUSE:Linux Enterprise Server 16.0 | All versions | 0.12.9-160000.3.1 |
| `editorconfig-core-c` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 0.12.9-160000.3.1 |
| `editorconfig-core-c` | openSUSE:Leap 16.0 | All versions | 0.12.9-160000.3.1 |
| `editorconfig-core-c` | openSUSE:Tumbleweed | All versions | 0.12.11-1.1 |

## How do I fix CVE-2026-40489?

Upgrade to a fixed version.

## Is CVE-2026-40489 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40489 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40489 and fix it if it is affected.

What it is: CVE-2026-40489 is a high-severity vulnerability in editorconfig-core-c, published on 18 Apr 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40489 exists.

Affected product: editorconfig-core-c. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40489/ (Markdown: https://insights.sbomify.com/CVE-2026-40489/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40489
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40489
- OSV: https://osv.dev/vulnerability/CVE-2026-40489

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40489/
Summaries are generated and may contain mistakes; the official description above is the record.