CVE-2026-48031

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

June 10, 2026

Last Modified

August 3, 2026

Advisory Details (3)

Auto-updated Aug 3, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit.
github_commit

commit cc82b9740fa6 (dhax/go-base)

Fix landed in dhax/go-base commit cc82b9740fa6 — awaiting tagged release

https://github.com/dhax/go-base/commit/cc82b9740fa6b08e0fad409cd4b418e240dd0e00
github_pr

Fix hardcoded JWT secret 'random' in dev.env and Viper default (CWE-798)

Fix merged in dhax/go-base PR #31 on 2026-05-17 — awaiting tagged release

https://github.com/dhax/go-base/pull/31
github Patch Available🟡 PoC Available

CWE-798: Hardcoded JWT Secret "random" allows token forgery (CVSS 9.1) · Advisory · dhax/go-base · GitHub

https://github.com/dhax/go-base/security/advisories/GHSA-mqq6-462x-jxmm

Vendor Advisories for CVE-2026-48031(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/dhax/go-base—0.0.0-20260517152733-cc82b9740fa6—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 00:29 UTCEG score recompute
  3. 2026-08-23 10:50 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 00:58 UTCEG score recompute
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 08:53 UTCEG score recompute
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 15:00 UTCEG score recompute
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 14:48 UTCEG score recompute
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 15:11 UTCEG score recompute
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 03:49 UTCEG score recompute
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 05:58 UTCEG score recompute
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-13 22:17 UTCEG score recompute
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-12 14:50 UTCEG score recompute
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-11 15:03 UTCEG score recompute
  25. 2026-08-11 03:41 UTCEG score recompute
Show 22 more
  1. 2026-08-11 00:00 UTCEPSS rescore
  2. 2026-08-09 15:56 UTCEG score recompute
  3. 2026-08-09 13:46 UTCEPSS rescore
  4. 2026-08-08 17:13 UTCEG score recompute
  5. 2026-08-08 16:37 UTCEPSS rescore
  6. 2026-08-07 18:28 UTCEG score recompute
  7. 2026-08-06 14:59 UTCEG score recompute
  8. 2026-08-06 13:47 UTCEPSS rescore
  9. 2026-08-05 20:02 UTCEG score recompute
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-04 15:56 UTCEG score recompute
  12. 2026-08-04 15:10 UTCEPSS rescore
  13. 2026-08-04 00:09 UTCEG score recompute
  14. 2026-08-03 20:21 UTCEG score recompute
  15. 2026-08-03 20:14 UTCEG score recompute
  16. 2026-07-30 09:55 UTCEG score recompute
  17. 2026-07-26 21:04 UTCEG score recompute
  18. 2026-07-23 03:18 UTCEG score recompute
  19. 2026-06-14 23:18 UTCEPSS rescore
  20. 2026-06-13 23:00 UTCEPSS rescore
  21. 2026-06-12 23:12 UTCEPSS rescore
  22. 2026-06-10 14:17 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48031?
CVE-2026-48031 is a critical vulnerability published on June 10, 2026. 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…
When was CVE-2026-48031 disclosed?
CVE-2026-48031 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48031 actively exploited?
CVE-2026-48031 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.9% of all scored CVEs.
What is the CVSS score of CVE-2026-48031?
CVE-2026-48031 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-48031?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48031, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48031

Explore →

Is Your Infrastructure Affected by CVE-2026-48031?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs