PatchSiren cyber security CVE debrief
CVE-2026-111633 SeriaWei CVE debrief
CVE-2026-111633 is an authentication bypass vulnerability in ZKEACMS through version 4.4. The vulnerability allows unauthenticated attackers to forge REST API JWT bearer tokens using a hard-coded HMAC-SHA256 signing key in JwtBearerDefaults.cs. This could lead to unauthorized access to sensitive data, modification of articles and products, and reading of form submissions. Defenders should assess exposure and prioritize updating to a fixed version. The CVE record and source item provide details on the vulnerability, including the hard-coded JWT signing key and the potential impact on ZKEACMS users.
- Vendor
- SeriaWei
- Product
- ZKEACMS
- CVSS
- HIGH 8.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-16
- Original CVE updated
- 2026-10-23
- Advisory published
- 2026-10-16
- Advisory updated
- 2026-10-23
Who should care
Defenders responsible for ZKEACMS deployments should assess exposure and prioritize updating to a fixed version. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Additionally, defenders should verify the authenticity of JWT tokens and monitor for potential exploitation attempts.
Why it matters
CVE-2026-111633 is a high-severity authentication bypass vulnerability in ZKEACMS through version 4.4, allowing unauthenticated attackers to forge REST API JWT bearer tokens.
- Potential unauthorized access to sensitive data
- Possible modification of articles and products
- Potential reading of form submissions
Technical summary
The vulnerability is caused by a hard-coded HMAC-SHA256 signing key in JwtBearerDefaults.cs, which allows unauthenticated attackers to forge REST API JWT bearer tokens. This could lead to unauthorized access to sensitive data, modification of articles and products, and reading of form submissions. The vulnerability has a high CVSS score of 8.8 and is considered a high-severity issue. Defenders should prioritize verifying the authenticity of JWT tokens and updating to a fixed version of ZKEACMS. The CVE record and source item provide additional information on the vulnerability.
Defensive priority
Defenders should prioritize verifying the authenticity of JWT tokens and updating to a fixed version of ZKEACMS.
Recommended defensive actions
- Verify the authenticity of JWT tokens in ZKEACMS
- Update to a fixed version of ZKEACMS
- Monitor for potential exploitation attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and source item provide details on the vulnerability, including the hard-coded JWT signing key and the potential impact on ZKEACMS users. The vulnerability has a high CVSS score of 8.8 and is considered a high-severity issue. There are no known instances of exploitation, but defenders should verify the authenticity of JWT tokens and update to a fixed version of ZKEACMS. The source item provides additional information on the vulnerability, including a technical description of the issue.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-111633 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-111633
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-111633 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-111633
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
ZKEACMS through 4.4 Authentication Bypass via Hard-Coded JWT Signing Key
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/111xxx/CVE-2026-111633.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://hackmd.io/@hieuPenguinnn/zkeacms-hardcoded-jwt-signing-key-admin-auth-bypass
Supplemental source - third-party-advisory
-
Source reference
Unverified legacy reference
URL: https://github.com/SeriaWei/ZKEACMS/blob/v4.4/src/ZKEACMS/Api/JwtBearerDefaults.cs
Supplemental source - technical-description
-
Source reference
Unverified legacy reference
URL: https://github.com/SeriaWei/ZKEACMS/blob/v4.4/src/ZKEACMS/BuilderAuthentication.cs
Supplemental source - technical-description
-
Source reference
Unverified legacy reference
URL: https://github.com/SeriaWei/ZKEACMS/issues/531
Supplemental source - issue-tracking
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/zkeacms-through-4.4-authentication-bypass-via-hard-coded-jwt-signing-key
Supplemental source - third-party-advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.