CVE-2023-26112 is a medium-severity (CVSS 5.9) CWE-1333 vulnerability in configobj. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for configobj — see the affected versions and patch details below.
configobj ReDoS exploitable by developer using values in a server-side configuration file
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-26112.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
configobjReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
All versions of the package configobj are vulnerable to Regular Expression Denial of Service (ReDoS) via the validate function, using (.+?)((.*)).
Note: This is only exploitable in the case of a developer, putting the offending value in a server side configuration file.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | configobj | all versions | 5.0.9pip install --upgrade 'configobj==5.0.9' |
Affected Products
configobjconfigobj_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for configobj, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update configobj to 5.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-26112 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2023-26112 in your dependencies?
Find it across PyPI, including transitive dependencies.