LiveActive security incident?Get immediate response
CVE Record

CVE-2026-33896: Forge has a basicConstraints bypass in its certificate chain verification (RFC 5280 violation)

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.4.0, `pki.verifyCertificateChain()` does not enforce RFC 5280 basicConstraints requirements when an intermediate certificate lacks both the `basicConstraints` and `keyUsage` extensions. This allows any leaf certificate (without these extensions) to act as a CA and sign other certificates, which node-forge will accept as valid. Version 1.4.0 patches the issue.

HighCVSS 7.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Some applications using node-forge could trust a certificate chain they should reject. In affected versions, a certificate that is not marked as a certificate authority may still be accepted as one under specific conditions. That can undermine identity checks where forge is used for certificate validation.

Executive priority

Prioritize remediation for internet-facing or security-sensitive systems that rely on node-forge certificate validation. Treat this as high priority for authentication, trust, or encrypted-traffic workflows. Systems with only unused or development-only forge dependencies can be handled after confirming non-exposure.

Technical view

Before forge 1.4.0, pki.verifyCertificateChain() does not enforce RFC 5280 basicConstraints when an intermediate certificate lacks both basicConstraints and keyUsage. A non-CA certificate without those extensions can sign other certificates and be accepted by node-forge. This is CWE-295 with CVSS 3.1 score 7.4.

Likely exposure

Exposure is most likely in applications or dependencies using digitalbazaar forge/node-forge below 1.4.0 for certificate chain validation, especially where pki.verifyCertificateChain() influences trust decisions. Exposure is lower where forge is present but not used for certificate verification.

Exploitation context

The bundle does not report active exploitation, and KEV is false. Exploitation requires an attacker to supply or influence certificate chains evaluated by affected forge code. The CVSS vector marks attack complexity high but no privileges or user interaction required.

Researcher notes

The key condition is absence of both basicConstraints and keyUsage on the intermediate being evaluated. The available sources identify the fixed upstream version and commit, but this analysis does not infer affected downstream products beyond the listed forge package and cited Red Hat materials.

Mitigation direction

  • Upgrade forge/node-forge to version 1.4.0 or later.
  • Review lockfiles and transitive dependencies for forge versions below 1.4.0.
  • Redeploy applications that bundle affected forge versions.
  • Check Red Hat advisories if consuming Red Hat-packaged components.
  • Follow vendor guidance for any downstream products embedding forge.

Validation and detection

  • Inventory package manifests and lockfiles for forge or node-forge below 1.4.0.
  • Search application code for pki.verifyCertificateChain() usage.
  • Confirm certificate validation paths use the updated library at runtime.
  • Add regression coverage for rejecting non-CA signing certificates.
  • Review Red Hat VEX or errata applicability for deployed platforms.
Prepared
Confidence
high
Sources
11

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-295: 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-33896 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
High
CVSS
7.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

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.

2CVSS vectors
5Timeline events
2ADP providers
10Source links

SSVC decision data

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

CVSS vector scores

2 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
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2GitHub_M
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2026-33896Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

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

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

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

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPnode-forge: Forge (node-forge): Certificate validation bypass allows unauthorized certificate issuance
other:Red Hat severity ratingcvssV3_1
  • 2026-03-27T21:02:22.762Z: Reported to Red Hat.
  • 2026-03-27T20:50:03.418Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
digitalbazaarforge< 1.4.0Listed
Weakness

CWE details

CWE-295

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

CWE-295 · source CWE mapping

Improper Certificate Validation

Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs