CVE-2026-48031
CRITICALDescription
go-base is a Go RESTful API Boilerplate template with JWT Authentication, backed by PostgreSQL. In versions prior to 2026-05-18, the JWT signing secret is hardcoded to the known string "random", letting any attacker who reads the public repository forge tokens for arbitrary users, including admin roles, and completely bypass authentication on all protected endpoints. This value is set in two places: the dev.env template (line 10) and a programmatic fallback in cmd/serve.go (line 35), so the application uses it even when no .env file is present. The original mitigation in auth/jwt/tokenauth.go (lines 22 to 25) only caught the exact string "random", letting other weak secrets through, and replaced it with an in-memory key that was not persisted, invalidating all tokens on every restart and effectively causing a denial-of-service. This issue has been fixed in version 2026-05-18.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 27% of all known CVEs.
References
Related Vulnerabilities
Other CWE-798 (Hard-coded Credentials) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-26138 | Critical | 9.8 | 98% | KEV | - |
| CVE-2024-3272 | Critical | 9.8 | 98% | KEV | - |
| CVE-2019-15975 | Critical | 9.8 | 96% | - | Fix |
| CVE-2025-30406 | Critical | 9.0 | 94% | KEV | Fix |
| CVE-2024-28987 | Critical | 9.1 | 93% | KEV | Fix |
| CVE-2019-15976 | Critical | 9.8 | 93% | - | Fix |
Common questions
How do I fix CVE-2026-48031?
No published fix for CVE-2026-48031 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-48031 being actively exploited?
Not that we know of. CVE-2026-48031 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.35% is the estimated probability that it will be exploited in the next 30 days. That is higher than 27% of all scored CVEs.
How severe is CVE-2026-48031?
CVE-2026-48031 has a CVSS v3 base score of 9.1, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-48031
Markdown
[](https://tridentstack.com/cve/CVE-2026-48031)HTML
<a href="https://tridentstack.com/cve/CVE-2026-48031"><img src="https://tridentstack.com/cve/badge/CVE-2026-48031.svg" alt="CVE-2026-48031"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-03.