CVE-2026-61737

waiting for further signalsZero needs more public information before it can validate it.

GHSA-qphq-m2hv-wj5h ↗EUVD-2026-114000 ↗

no check availablenot proven exploitable
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.
huajian123 ng-antd-admin <22.0
fixed in 22.0
CWE-321 Use of Hard-coded Cryptographic Key
ETK-2026-3089Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/ng-antd-admin nestjsapi
2h 49msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h28m
0
+4h
+6h
+8h
+10h
+12h

description

ng-antd-admin versions before 22.0 can accept JWTs derived from a shipped signing secret. An unauthenticated attacker may gain access as arbitrary users, including administrators, when the deployment has not replaced that default secret.

mitigation

Upgrade ng-antd-admin to version 22.0. Immediately replace any default JWT signing secret with a unique secret and invalidate or rotate existing tokens.

fixed in 22.0

check
no
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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 14:34Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-30 14:34Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3089",
  "cve_id": "CVE-2026-61737",
  "display_id": "CVE-2026-61737",
  "ghsa_id": "GHSA-qphq-m2hv-wj5h",
  "euvd_id": "EUVD-2026-114000",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hardcoded JWT secret authentication bypass in ng-antd-admin",
  "summary": "ng-antd-admin versions before 22.0 can accept JWTs derived from a shipped signing secret. An unauthenticated attacker may gain access as arbitrary users, including administrators, when the deployment has not replaced that default secret.",
  "mitigation": "Upgrade ng-antd-admin to version 22.0. Immediately replace any default JWT signing secret with a unique secret and invalidate or rotate existing tokens.",
  "vendor": "huajian123",
  "product": "ng-antd-admin",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<22.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "22.0"
      ],
      "package_name": "ng-antd-admin nestjsapi",
      "purl": "pkg:npm/ng-antd-admin nestjsapi"
    }
  ],
  "cwes": [
    321
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.441318766666665,
  "t0_at": "2026-10-30T14:34:03.817000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-30T14:34:03.817000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T14:34:03.817000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-61737"
    }
  }
}

published 2026-10-30 15:42Z
last change 2026-10-30 17:20Z

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.