Skip to main content
CVE-2023-0341VulnerabilityPublished Updated

CVE-2023-0341: EditorConfig C Core · CWE-121

Affects EditorConfig C CoreSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High : upgrade to 0.12.6 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.12.6
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jan 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade editorconfig/editorconfig-core-c to 0.12.6.

Affected software

ProductAffectedFixed in
GitHubeditorconfig/editorconfig-core-cpkg:github/editorconfig/editorconfig-core-cOther threatsAffected
  • <0.12.6
Fixed in
  • 0.12.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should immediately upgrade EditorConfig C Core to version 0.12.6 or later, where the buffer overflow issue has been fixed. Conduct a thorough inventory of all development and CI/CD environments to identify instances of EditorConfig C Core usage, including indirect dependencies in build tools and IDE plugins. Implement strict input validation and sandboxing for any processes that parse EditorConfig files, especially those sourced from untrusted or external contributors. Educate developers and DevOps teams about the risks of processing untrusted configuration files and enforce policies to verify the integrity of such files before use. Employ runtime protections such as stack canaries and address space layout randomization (ASLR) to reduce exploitation likelihood. Finally, integrate vulnerability scanning tools into the software supply chain to detect usage of vulnerable EditorConfig versions proactively.

Description

A stack buffer overflow exists in the ec_glob function of editorconfig-core-c before v0.12.6 which allowed an attacker to arbitrarily write to the stack and possibly allows remote code execution.editorconfig-core-c v0.12.6 resolved this vulnerability by bound checking all write operations over the p_pcre buffer.

References

Community reviews

Loading reviews…