CWE-319: Cleartext Transmission of Sensitive Information in gofiber fiber (CVE-2026-53624)
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.
AI Analysis
Technical Summary
The gofiber framework's helmet middleware (middleware/helmet/helmet.go) prior to version 3.4.0 does not set the Strict-Transport-Security response header when HSTSMaxAge is configured. This is due to the middleware checking c.Protocol() for 'https' instead of c.Scheme(), causing the HSTS header to be omitted. The absence of this header can allow sensitive information to be transmitted over unencrypted HTTP connections. This vulnerability is classified under CWE-319 (Cleartext Transmission of Sensitive Information) and has a CVSS 3.1 base score of 4.8 (medium severity). The issue is resolved in gofiber version 3.4.0.
Potential Impact
Without the Strict-Transport-Security header being set, clients may not enforce HTTPS connections, potentially allowing sensitive information to be transmitted in cleartext over HTTP. This can increase the risk of interception or man-in-the-middle attacks. The CVSS score reflects a moderate impact with low confidentiality and integrity impact and no availability impact.
Mitigation Recommendations
Upgrade gofiber to version 3.4.0 or later, where the helmet middleware correctly sets the Strict-Transport-Security header when configured. No other mitigation is indicated by the vendor advisory.
CWE-319: Cleartext Transmission of Sensitive Information in gofiber fiber (CVE-2026-53624)
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.
CVSS v3.1
Score 4.8medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The gofiber framework's helmet middleware (middleware/helmet/helmet.go) prior to version 3.4.0 does not set the Strict-Transport-Security response header when HSTSMaxAge is configured. This is due to the middleware checking c.Protocol() for 'https' instead of c.Scheme(), causing the HSTS header to be omitted. The absence of this header can allow sensitive information to be transmitted over unencrypted HTTP connections. This vulnerability is classified under CWE-319 (Cleartext Transmission of Sensitive Information) and has a CVSS 3.1 base score of 4.8 (medium severity). The issue is resolved in gofiber version 3.4.0.
Potential Impact
Without the Strict-Transport-Security header being set, clients may not enforce HTTPS connections, potentially allowing sensitive information to be transmitted in cleartext over HTTP. This can increase the risk of interception or man-in-the-middle attacks. The CVSS score reflects a moderate impact with low confidentiality and integrity impact and no availability impact.
Mitigation Recommendations
Upgrade gofiber to version 3.4.0 or later, where the helmet middleware correctly sets the Strict-Transport-Security header when configured. No other mitigation is indicated by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gv83-gqw6-9j2c
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53624"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a4c340527e9c797195f64ad
Added to database: 07/06/2026, 23:02:29 UTC
Last enriched: 07/14/2026, 07:52:26 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 82
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.