CVE-2026-62374

validatedZero produced an exploit or a check.

GHSA-f9j6-8p6x-r9j6 ↗EUVD-2026-113215 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
npm:@sd-jwt/decode <= 0.19.0
fixed in 0.20.0
ETK-2026-3329Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/@sd-jwt/decode
pkg:npm/@sd-jwt/core
+4.4dTTV
31mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0dcheck available+4.4dagent stopped
0
+1d
+2d
+3d
+4d

description

Versions through 0.19.0 of @sd-jwt/decode, as used by affected @sd-jwt/core deployments, may process altered SD-JWT disclosures without rejecting the presentation and omit the corresponding claims. A holder can submit such a presentation to influence decisions that treat missing restrictive claims as acceptable; a network attacker also needs key binding to be disabled.

mitigation

Upgrade @sd-jwt/core to 0.20.0 or later. Replace or avoid standalone @sd-jwt/decode for verification until it has a recorded fixed release, and require key binding to limit network-based alteration.

fixed in 0.20.0

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 16:27Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-29 16:27Z
    ghsa: trigger signal, started the run
  2. 2026-10-29 16:27Z

this entry in the feed

GET /api/v1/feed/CVE-2026-62374

{
  "etk_id": "ETK-2026-3329",
  "cve_id": "CVE-2026-62374",
  "display_id": "CVE-2026-62374",
  "ghsa_id": "GHSA-f9j6-8p6x-r9j6",
  "euvd_id": "EUVD-2026-113215",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Tampered disclosure omission in @sd-jwt/decode",
  "summary": "Versions through 0.19.0 of @sd-jwt/decode, as used by affected @sd-jwt/core deployments, may process altered SD-JWT disclosures without rejecting the presentation and omit the corresponding claims. A holder can submit such a presentation to influence decisions that treat missing restrictive claims as acceptable; a network attacker also needs key binding to be disabled.",
  "mitigation": "Upgrade @sd-jwt/core to 0.20.0 or later. Replace or avoid standalone @sd-jwt/decode for verification until it has a recorded fixed release, and require key binding to limit network-based alteration.",
  "vendor": "npm",
  "product": "npm:@sd-jwt/decode",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 0.19.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [],
      "package_name": "@sd-jwt/decode",
      "purl": "pkg:npm/@sd-jwt/decode"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 0.19.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "0.20.0"
      ],
      "package_name": "@sd-jwt/core",
      "purl": "pkg:npm/@sd-jwt/core"
    }
  ],
  "cwes": null,
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 31.02819245,
  "t0_at": "2026-10-29T16:27:40.825000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-03T01:48:53.388225+00:00",
      "days": 4.389728741030092,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T16:27:40.825000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-29T16:27:40.825000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T16:27:40.825000+00:00",
      "url": "https://github.com/advisories/GHSA-f9j6-8p6x-r9j6"
    }
  }
}

published 2026-11-03 00:47Z
last change 2026-11-03 03:18Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.