Security readout for executives and security teams
Plain-English summary
Deno before 2.6.0 has a critical flaw in its Node-compatible crypto implementation. Cipher operations may not be finalized correctly, potentially letting an attacker perform unlimited encryption attempts and work toward learning server secrets. Organizations using Deno for cryptographic functions or exposed services should treat this as urgent.
Executive priority
High priority. Patch affected Deno deployments promptly, starting with exposed applications handling encryption or secrets. No public exploitation is cited, but the stated confidentiality impact is severe.
Technical view
CVE-2026-22863 affects denoland Deno versions before 2.6.0. The issue is in node:crypto cipher finalization and is classified as CWE-325. The CVSS 4.0 score is 9.2, with network attackability, low complexity, no privileges, and high confidentiality impact. The vendor states it is fixed in Deno 2.6.0.
Likely exposure
Exposure is likely where Deno versions earlier than 2.6.0 run applications using node:crypto, especially services that perform encryption for remote users or process attacker-influenced data.
Exploitation context
The source bundle does not report active exploitation, and the CVE is not marked KEV. The advisory describes risk from unlimited encryptions, including brute-force attempts and more refined attacks to learn server secrets.
Researcher notes
Evidence is limited to the CVE record, GitHub advisory, and Deno 2.6.0 release reference. The public bundle does not include proof-of-concept details, exploit telemetry, or compensating mitigations beyond upgrading.
Mitigation direction
- Upgrade Deno to version 2.6.0 or later.
- Prioritize internet-facing Deno services using node:crypto.
- Review the GitHub security advisory for vendor-specific guidance.
- Assess whether exposed secrets require incident response actions.
Validation and detection
- Inventory Deno runtime versions across production and CI systems.
- Identify applications importing or depending on node:crypto.
- Confirm affected systems run Deno 2.6.0 or later.
- Review logs for unusual encryption request patterns.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-325: 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 lookupCVE-2026-22863 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/denoland/deno/security/advisories/GHSA-5379-f5hf-w38vCVE reference · x_refsource_CONFIRM
- https://github.com/denoland/deno/releases/tag/v2.6.0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Cryptographic Step
Missing Cryptographic Step represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.