CVE-2026-56100
Authenticated JWT forgery enables admin account creation via exposed Feign endpoint.
Is CVE-2026-56100 being exploited?
Not confirmed. CVE-2026-56100 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-56100?
CVE-2026-56100 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-56100?
Yes. A fix has been recorded for CVE-2026-56100. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56100 affect?
CVE-2026-56100 affects SpringBlade 2.7.3 through <5.0.0, Applications using SpringBlade Feign user-creation endpoint. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56100?
Upgrade to SpringBlade 5.0.0, rotate JWT signing keys, audit and remove unauthorized admin accounts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Forge hardcoded JWT to call exposed Feign user-creation endpoint, create admin accounts, escalate privileges, enable cross-tenant data access and persistent backdoors.
Immediate action required
- affected>= 2.7.3 and < 5.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.