// 1 CRITICAL · 3 ZERO-DAY · 5 CVE · 4 EXPLOIT IN THE LAST 24H
Singapore's Cyber Security Agency published an advisory on CVE-2026-3008, a string injection flaw in Notepad++ 8.9.3 with a CVSS 6.6 score. The fix was already available in version 8.9.4, released on April 26, 2026, while the CSA alert is dated August 19, 2026 — a procedural gap of over four months.

Singapore's Cyber Security Agency (CSA) published an advisory on August 19, 2026, for vulnerability CVE-2026-3008 in Notepad++ 8.9.3. The flaw is classified as CWE-134: Use of Externally-Controlled Format String. The issue allows memory address disclosure or application crashes. The patched version 8.9.4 was already available from April 26, 2026. The institutional alert arrives more than four months after the patch release and the CVE record publication, which occurred on April 27.

Key Takeaways
  • CVE-2026-3008 is a string injection flaw (CWE-134) in Notepad++ 8.9.3 with a CVSS 3.1 score of 6.6 (MEDIUM)
  • Exploitation requires local user interaction (UI:R, AV:L) and no elevated privileges; availability impact is rated high (A:H)
  • The fix is in version 8.9.4, released by the vendor on April 26, 2026; the CSA alert is dated August 19, 2026
  • EPSS is below 1%, the vulnerability does not appear in the CISA KEV catalog, and SSVC indicates automation is not possible

The Institutional Delay and the Correlation Gap

The timeline drawn from the sources reveals a significant gap. The CVE-2026-3008 record was published on April 27, 2026. The Notepad++ 8.9.4 release candidate was available from April 26. The CSA alert is dated August 19, 2026: over four months later. This delay is not technical — the patch already existed — but procedural.

A point of uncertainty remains in the dossier. The 8.9.4 release candidate changelog cites a fix for "crash caused by undoing column editor bad input in virtual space." The Notepad++ community source does not verify whether this entry corresponds directly to CVE-2026-3008 or to a related but distinct vulnerability class. The CSA advisory identifies 8.9.4 as the fixed version with certainty, but the precise mapping between the public changelog and the CVE remains unconfirmed. This limitation is typical of community sources, which do not guarantee formal traceability.

The phenomenon raises questions about the chain of responsibility in open-source vulnerability disclosure. As the CVE assigner, the CSA likely followed its own validation and publication timelines. The four-month interval signals a systemic friction between open-source development speed and government agency cadence.

The Mechanics of the Flaw: What the Sources Report

The technical brief indicates CWE-134 and "string injection flaw" as the vulnerability classification. The CVSS 3.1 vector confirms the local nature of the attack: AV:L means the attacker must already have access to the target system. The UI:R requirement mandates user interaction, reducing the automatable attack surface.

The combination C:L/I:L/A:H is significant: low impact on confidentiality and integrity, but high availability. The CSA description states that exploitation "could allow an attacker to obtain memory address information or crash the application." The brief does not specify exploit chains or additional bypass techniques.

"Successful exploitation of the string injection vulnerability could allow an attacker to obtain memory address information or crash the application."
— Cyber Security Agency of Singapore, AL-2026-044

Current Risk and Threat Intelligence Indicators

Threat intelligence data converges on a contained assessment. EPSS registers a value below 1% for CVE-2026-3008. The vulnerability is not present in the CISA KEV catalog. The SSVC indicated by OpenCVE classifies automation as "no" and technical impact as "partial."

The SSVC field reports "poc" for exploitation, but the brief does not verify whether a public PoC exists, linked or documented. This indicator does not confirm that exploitation is technically replicable without further information. The combination of a local attack vector and required user interaction constitutes operational barriers for an attacker.

Action Items

  • Verify the installed Notepad++ version and update to 8.9.4 or later, as recommended by the CSA advisory
  • Note that the CSA source was published on August 19, 2026, with over four months of delay relative to fix availability
  • Bear in mind that the community source (Notepad++ 8.9.4 RC2 changelog) does not formally confirm the mapping between the cited fix and CVE-2026-3008

Source Limitations and Editorial Validation

The dossier rests on two structured primary sources: the CSA advisory and the OpenCVE record. The CSA advisory, despite being the CVE assigner, was published with significant delay relative to patch availability. The OpenCVE record reports a CVSS 4.0 score of 10.0 that appears anomalous and potentially erroneous; official sources converge on CVSS 3.1 at 6.6.

The community source (deleted topic on community.notepad-plus-plus.org) provides temporal context on the 8.9.4 release but does not verify the direct link to CVE-2026-3008. Organizations must evaluate this uncertainty within their own patch management cycles.

Editor's note: Information on the CSA advisory has been validated against the publication date of August 19, 2026, with awareness of the four-month delay relative to the vendor fix. The CVSS 3.1 score of 6.6 is the convergent data point between CVE.org and NVD, after correction of an initially erroneous 4.0 value.

Sources

Information has been verified against cited sources and updated at time of publication.

Sources


Sources and references
  1. csa.gov.sg
  2. app.opencve.io
  3. cve.org
  4. nvd.nist.gov
  5. community.notepad-plus-plus.org