Approved changes feed: RSS · Atom
cpe:2.3:a:dhax:go-base:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Dhax (6df50b5d-f40a-5205-a813-21b09b2aee8c) |
|---|---|
| Product | Go Base (17baec42-2cc3-53d3-9906-233f76ea7af2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-48031 |
vulnerable | 2026-09-16 04:33:04.600013 |
Go Restful API Boilerplate: Hardcoded JWT Secret "random" Allows Token Forgery
CRITICAL (9.1)
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.
Published: 2026-08-03T19:05:50.679Z
Updated: 2026-08-03T19:49:15.909Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.