CVE-2026-3384
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security vulnerability has been detected in ChaiScript up to 6.1.0. This impacts the function chaiscript::eval::AST_Node_Impl::eval/chaiscript::eval::Function_Push_Pop of the file include/chaiscript/language/chaiscript_eval.hpp. The manipulation leads to uncontrolled recursion. An attack has to be approached locally. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceChaiScript versions up to 6.1.0 contain an uncontrolled recursion vulnerability in the AST evaluation functions (chaiscript::eval::AST_Node_Impl::eval and Function_Push_Pop) within chaiscript_eval.hpp. By providing a specially crafted script with deeply nested expressions, an attacker can trigger stack overflow, leading to denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 6.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ChaiScript installation and versionLocate the ChaiScript library in your environment (check project dependencies, package managers, or bundled libraries). Identify the installed version number (typically found in headers, library metadata, or build files).Affected if The installed version is ChaiScript at version 6.1.0 or any earlier version.
-
Verify vulnerable source file is presentLocate the chaiscript_eval.hpp header file in your ChaiScript installation. Search for the functions AST_Node_Impl::eval and Function_Push_Pop within this file.Affected if These functions exist in the codebase with recursive implementation and no apparent depth limiting guards.
-
Confirm AST evaluation is in useIdentify if your application or system loads and executes ChaiScript scripts. Check for code that calls eval(), eval_with_return(), or similar API functions that trigger AST traversal.Affected if Scripts are being evaluated through the recursive AST evaluation functions in chaiscript_eval.hpp.
-
Check for recursion depth limitingSearch the ChaiScript source code and configuration for any recursion depth limits, stack size controls, or iterative traversal implementations. Look for max_depth, stack_limit, or similar parameters.Affected if No recursion depth limit is found in the code or configuration, meaning deeply nested expressions can trigger unbounded recursion.
Your environment is affected if ChaiScript version 6.1.0 or earlier is installed and scripts are evaluated using the recursive AST evaluation functions without depth limiting protections.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement recursion depth limiting or convert the recursive AST evaluation to an iterative approach with explicit stack management to prevent stack exhaustion from maliciously crafted scripts.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3384 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3384 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data