CVE-2026-48031
Hardcoded JWT secret 'random' allows token forgery and full auth bypass.
Is CVE-2026-48031 being exploited?
Not confirmed. CVE-2026-48031 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.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-48031?
CVE-2026-48031 is rated Critical with a CVSS score of 9.1. 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-48031?
Yes. A fix has been recorded for CVE-2026-48031. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-48031 affect?
CVE-2026-48031 affects go-base (Go RESTful API Boilerplate) < 2026-05-18, Applications built from affected go-base template. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48031?
Upgrade to go-base 2026-05-18, rotate JWT secrets, revoke existing tokens.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can forge JWTs to impersonate any user (including admins), bypass authentication, and access or modify protected API endpoints.
Immediate action required
- affected2026-05-18
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.