SpringBlade versions 2.7.3 through 3.5.0 contain a privilege escalation vulnerability that allows authenticated attackers to create system… (CVE-2026-56100)
Description
SpringBlade versions 2.7.3 through 3.5.0 have a privilege escalation vulnerability allowing authenticated attackers to create system administrator accounts via an unprotected internal user-creation endpoint. The flaw arises from insufficient authorization checks on a Feign endpoint exposed through @RestController and a gateway authentication filter that validates JWT parsing but does not verify user roles or caller identity. Attackers can exploit a hardcoded JWT signing key found in publicly available JARs to forge tokens and escalate privileges, potentially causing cross-tenant data pollution and persistent backdoor access.
CVSS v3.1
Score 8.1high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-56100 affects SpringBlade versions 2.7.3 through 3.5.0. The vulnerability is a privilege escalation issue where authenticated users can create system administrator accounts by sending crafted POST requests to an internal Feign user-creation endpoint exposed without authorization checks via @RestController. The gateway's authentication filter only validates JWT parsing but does not verify user roles or caller identity. A hardcoded JWT signing key embedded in publicly available JARs enables attackers to forge tokens, escalate privileges from low-privilege users to administrators, and maintain persistent unauthorized access, including cross-tenant data pollution.
Potential Impact
Exploitation allows authenticated attackers to escalate privileges to system administrator level, enabling unauthorized creation of admin accounts. This can lead to cross-tenant data pollution and persistent backdoor access, severely compromising system integrity and confidentiality. The CVSS 3.1 score of 8.1 reflects high impact on confidentiality and integrity with network attack vector and low attack complexity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the affected endpoints and review JWT signing key management to prevent token forgery. Monitor for suspicious account creation activities and consider implementing additional authorization checks on internal endpoints.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-pmhv-3rpv-4cgh
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-56100"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a92f7efacd9273b49e78a1d
Added to database: 08/29/2026, 15:17:03 UTC
Last enriched: 09/08/2026, 02:22:13 UTC
Last updated: 10/12/2026, 06:48:17 UTC
Views: 41
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.