Fiber: HSTS header never set in helmet middleware due to incorrect protocol check
Summary
| CVE | CVE-2026-53624 |
|---|---|
| State | PUBLISHED |
| Assigner | GitHub_M |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-08 20:16:52 UTC |
| Updated | 2026-07-10 16:16:32 UTC |
| Description | Fiber is an Express inspired web framework written in Go. Prior to 3.4.0, the helmet middleware in middleware/helmet/helmet.go never sets the Strict-Transport-Security response header even when HSTSMaxAge is configured because it checks c.Protocol() for https instead of c.Scheme(). This issue is fixed in version 3.4.0. |
Risk And Classification
Primary CVSS: v3.1 4.8 MEDIUM from [email protected]
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS: 0.002070000 probability, percentile 0.108330000 (date 2026-07-09)
Problem Types: CWE-319 | CWE-319 CWE-319: Cleartext Transmission of Sensitive Information
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 4.8 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N |
| 3.1 | CNA | DECLARED | 4.8 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
HighPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
LowIntegrity
LowAvailability
NoneCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/gofiber/fiber/pull/4389 | [email protected] | github.com | |
| github.com/gofiber/fiber/commit/04dd4e7754f61768fddccacc79057e416f13e6bf | [email protected] | github.com | |
| github.com/gofiber/fiber/security/advisories/GHSA-gv83-gqw6-9j2c | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | github.com | |
| github.com/gofiber/fiber/releases/tag/v3.4.0 | [email protected] | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.