LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24797: An out of bounds write due to a missing bounds check in neka-nat/cupoch

Out-of-bounds Write vulnerability in neka-nat cupoch (third_party/libjpeg-turbo/libjpeg-turbo modules). This vulnerability is associated with program files tjbench.C. This issue affects cupoch.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24797 is a memory corruption issue in neka-nat cupoch, tied to bundled libjpeg-turbo code and tjbench.C. An attacker could potentially cause limited integrity or availability impact if the vulnerable component is reachable. Public sources do not show active exploitation.

Executive priority

Treat as a moderate-priority remediation item. Prioritize sooner where cupoch processes untrusted data or is exposed through automated services. There is no sourced evidence of active exploitation, but memory corruption flaws can create operational risk if reachable.

Technical view

The CVE describes a CWE-787 out-of-bounds write caused by a missing bounds check in cupoch third_party/libjpeg-turbo/libjpeg-turbo modules, associated with tjbench.C. CVSS 4.0 score is 6.9 with network attack vector, low complexity, no privileges, and no user interaction. The only provided remediation reference is GitHub pull request #138.

Likely exposure

Exposure is likely limited to environments using neka-nat cupoch where the affected bundled libjpeg-turbo/tjbench.C code is present, built, or reachable. The source data lists cupoch as affected but does not provide a fixed release, package ecosystem details, or deployment-specific exposure conditions.

Exploitation context

No KEV listing is present, and the provided sources do not claim active exploitation or public weaponization. The CVSS vector indicates remote, low-complexity conditions without privileges or user interaction, but the practical attack surface depends on how cupoch is deployed and invoked.

Researcher notes

The public record is sparse. Affected version data is listed only as cupoch version “0,” and no fixed release is named in the bundle. The patch reference is PR #138; validate its merge status and exact code changes before making remediation assertions.

Mitigation direction

  • Review GitHub pull request #138 and apply vendor-approved patch guidance.
  • Check upstream cupoch advisories for a fixed release or commit.
  • Reduce exposure of affected cupoch components to untrusted inputs until remediated.
  • Track this in dependency and third-party source remediation workflows.

Validation and detection

  • Inventory systems, containers, and source trees using neka-nat cupoch.
  • Confirm whether affected libjpeg-turbo/tjbench.C code is present or built.
  • Compare deployed code against the changes in pull request #138.
  • Verify any vendor-recommended fixed version or commit before closing the finding.
Prepared
Confidence
medium
Sources
3

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-787: 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-24797 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
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L/AU:Y/R:A/RE:M/U:Amber

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

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
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L/AU:Y/R:A/RE:M/U:Amber——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

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

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L/AU:Y/R:A/RE:M/U:Amber

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
neka-natcupoch0affected
Weakness

CWE details

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

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.