VulnerabilityPublished 30 Sep 2026Updated 2 Oct 2026

CVE-2026-102804: Nothings stb · Integer Overflow

Affects Nothings stbSource CVE Database V5

Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS

0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: Proof of concept is public or traded
Automatable: Attackers can reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-02.

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 30 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CISA SSVC: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by VulDB
29 Sep 202617:08 UTC, 7 hours before disclosure
CVE published
on cve.org
30 Sep 202600:00 UTC, t = 0
CISA SSVC assessment
proof of concept public
2 Oct 202612:43 UTC, 2 days after disclosure
In Threat Radar
record ingested
26 Oct 202608:09 UTC, 26 days after disclosure

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

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Nothingsstb	Affected =2c980bb59875b0d32144a71867fbdebb2f77cd20	Fixed in–

CPE configurations (1)

cpe:2.3:a:nothings:stb:*:*:*:*:*:*:*:*

AI-suggested

Users should monitor the vendor's communications for updates. Until a fix is available, avoid using the affected function with untrusted input or consider applying manual input validation to prevent triggering the overflow.

Description

CVE-2026-102804 is an integer overflow vulnerability in the function hexwave_init within the stb_hexwave.h library of Nothings stb. The flaw occurs when manipulating the width or oversample arguments, potentially allowing remote exploitation. The vulnerability affects versions up to commit 2c980bb59875b0d32144a71867fbdebb2f77cd20. Public exploit code is available, but the project has not yet issued a response or patch.

Impact

The integer overflow may lead to memory corruption or other undefined behavior, potentially allowing remote attackers to execute arbitrary code or cause denial of service. The CVSS 4.0 score of 6.9 (medium severity) reflects the network attack vector with no privileges or user interaction required, but limited impact scope and complexity. Public exploit code availability increases the risk of exploitation.

Summary

This vulnerability involves an integer overflow in the hexwave_init function of the stb_hexwave.h component in Nothings stb. By manipulating the width or oversample parameters, an attacker can trigger an integer overflow condition. The vulnerability is remotely exploitable and public exploit code exists. The affected versions include all code up to commit 2c980bb59875b0d32144a71867fbdebb2f77cd20.

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

CPE configurations (1)

Description

AI analysisMachine-generated, updated 3 Nov 2026, 05:13 UTC

Technical details

References

Community reviews

Related threats