LiveActive security incident?Get immediate response
CVE Record

CVE-2026-3382: ChaiScript boxed_number.hpp get_as memory corruption

A security flaw has been discovered in ChaiScript up to 6.1.0. The impacted element is the function chaiscript::Boxed_Number::get_as of the file include/chaiscript/dispatchkit/boxed_number.hpp. Performing a manipulation results in memory corruption. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

MediumCVSS 4.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-3382 is a memory corruption flaw in ChaiScript, a C++ scripting library. An attacker needs local access and low privileges, so internet-facing exposure is unlikely. Public exploit material is reported, but CISA KEV does not list active exploitation. Business urgency is mainly for products embedding ChaiScript in local or user-scriptable workflows.

Executive priority

Prioritize assessment for products where local users can run or influence ChaiScript scripts. This is not currently evidenced as a remote mass-exploitation issue, but public exploit availability and no confirmed fix justify near-term inventory and containment.

Technical view

The flaw affects chaiscript::Boxed_Number::get_as in include/chaiscript/dispatchkit/boxed_number.hpp. Sources describe CWE-119 memory corruption in ChaiScript up to 6.1.0, including versions 6.0 and 6.1.0. CVSS 4.0 is 4.8 with AV:L/PR:L/UI:N and low availability impact. Vendor/project response or a fixed release is not confirmed in the provided sources.

Likely exposure

Exposure is limited to systems or applications that embed affected ChaiScript versions and allow local users or local code paths to exercise ChaiScript numeric conversions. Cloud, desktop, developer tooling, or appliance products may be affected if they bundle the library.

Exploitation context

The record says exploitation requires a local approach and low privileges. Public exploit material is reported in the issue/reference set, but KEV is false and no cited source confirms active exploitation in the wild. Treat public proof-of-concept availability as raising validation priority.

Researcher notes

Evidence is limited to CVE/VulDB data and the linked GitHub issue. Avoid assuming affected downstream products. The key unknown is whether a fix exists in a branch or release, because the sources state the project had not responded yet.

Mitigation direction

  • Inventory applications and products that embed or statically link ChaiScript.
  • Identify ChaiScript versions 6.0 through 6.1.0 in source, dependencies, and SBOMs.
  • Check the ChaiScript GitHub issue and project releases for official remediation guidance.
  • Restrict local access to systems running affected embedded scripting functionality.
  • Reduce exposure of user-controlled scripts until vendor guidance or a fix is available.

Validation and detection

  • Search repositories and SBOMs for ChaiScript and boxed_number.hpp.
  • Confirm embedded ChaiScript version in built artifacts, not only package manifests.
  • Review whether local users can submit or influence ChaiScript execution.
  • Monitor the referenced GitHub issue for maintainer response or patch commits.
  • Track VulDB and CVE records for severity, exploitation, or fix updates.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-119: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-3382 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

4CVSS vectors
6Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

4 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.8CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P——VulDB
3.3CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:X/RC:R1.81.4VulDB
3.3CVSS 3.0LowCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:P/RL:X/RC:R1.81.4VulDB
1.7CVSS 2.0LowAV:L/AC:L/Au:S/C:N/I:N/A:P/E:POC/RL:ND/RC:UR3.12.9VulDB

Vulnerability scoring details

Base CVSS 4.0 score

4.8Medium
CVSS 4.0 vector shape for CVE-2026-3382Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineVulDB

    Advisory disclosed

  2. Source timelineVulDB

    VulDB entry created

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timelineVulDB

    VulDB entry last update

  5. CVE publishedCVE Program

    The CVE record was published.

  6. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aChaiScript6.0, 6.1.0Listed
Weakness

CWE details

CWE-119

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-119 · source CWE mapping

Improper Restriction of Operations within the Bounds of a Memory Buffer

Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs