Skip to main content
VulnerabilityPublished

CVE-2026-61737: huajian123 ng-antd-admin · Use of Hard-coded Cryptographic Key

Affects huajian123 ng-antd-adminSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 22.0 as a priority.

Data as of 30 Oct 2026, 14:49 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.19.8
Patch
Available – fixed in 22.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade huajian123 ng-antd-admin to 22.0.

Affected software

ProductAffectedFixed in
huajian123ng-antd-adminAffected
  • <22.0
Fixed in
  • 22.0

AI-suggested

Upgrade to ng-antd-admin version 22.0 or later, which rejects the default hardcoded JWT secret in production environments and issues warnings in non-production environments. Ensure that the default secret is replaced with a secure, unique secret before deployment. No other mitigation is indicated by the vendor advisory.

Description

ng-antd-admin versions prior to 22.0 contain a hardcoded default JWT secret key, which allows attackers to forge tokens if the default secret is not replaced. This vulnerability enables bypassing authentication and authorization, impersonation of any user including administrators, and unauthorized access to protected API endpoints. Version 22.0 addresses this issue by rejecting the default secret in production environments and issuing warnings in non-production environments.

References

Community reviews

Loading reviews…