{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-61737", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-07-10T18:59:00.047Z", "datePublished": "2026-10-30T14:34:03.817Z", "dateUpdated": "2026-10-30T14:34:03.817Z"}, "containers": {"cna": {"title": "ng-antd-admin: Hardcoded JWT Secret allows Authentication Bypass in ng-antd-admin", "problemTypes": [{"descriptions": [{"cweId": "CWE-321", "lang": "en", "description": "CWE-321: Use of Hard-coded Cryptographic Key", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 9.8, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "version": "3.1"}}], "references": [{"name": "https://github.com/huajian123/ng-antd-admin/security/advisories/GHSA-qphq-m2hv-wj5h", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/huajian123/ng-antd-admin/security/advisories/GHSA-qphq-m2hv-wj5h"}, {"name": "https://github.com/huajian123/ng-antd-admin/commit/23e92ff9176074ee534af3ea3700b3652a9726a9", "tags": ["x_refsource_MISC"], "url": "https://github.com/huajian123/ng-antd-admin/commit/23e92ff9176074ee534af3ea3700b3652a9726a9"}, {"name": "https://github.com/huajian123/ng-antd-admin/releases/tag/v22.0", "tags": ["x_refsource_MISC"], "url": "https://github.com/huajian123/ng-antd-admin/releases/tag/v22.0"}], "affected": [{"vendor": "huajian123", "product": "ng-antd-admin", "versions": [{"version": "< 22.0", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-10-30T14:34:03.817Z"}, "descriptions": [{"lang": "en", "value": "ng-antd-admin is an Angular and NestJS administration system template. Prior to 22.0, a hardcoded default `JWT` secret permits token forgery when a deployment has not replaced the default secret, without a startup warning. An attacker can bypass authentication and authorization, impersonate any user including administrators, and access protected API endpoints, leading to account takeover, data leakage and unauthorized operations. Version 22.0 rejects the shipped secret in production but permits it with a warning in non-production environments."}], "source": {"advisory": "GHSA-qphq-m2hv-wj5h", "discovery": "UNKNOWN"}}}}

{}

{}

{}

{}