Untriaged
Permalink
CVE-2026-53624
4.8 MEDIUM
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Network (N)
- Attack Complexity (AC): High (H)
- Privileges Required (PR): None (N)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): Low (L)
- Integrity (I): Low (L)
- Availability (A): None (N)
- Modified Attack Vector (MAV): Network (N)
- Modified Attack Complexity (MAC): High (H)
- Modified Privileges Required (MPR): None (N)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): Low (L)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): Low (L)
- Modified Availability (MA): None (N)
Activity log
- Created suggestion
Fiber: HSTS header never set in helmet middleware due to incorrect protocol check
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.
References
-
https://github.com/gofiber/fiber/security/advisories/GHSA-gv83-gqw6-9j2c x_refsource_CONFIRM
-
https://github.com/gofiber/fiber/pull/4389 x_refsource_MISC
-
https://github.com/gofiber/fiber/releases/tag/v3.4.0 x_refsource_MISC
Affected products
fiber
- ==< 3.4.0
Matching in nixpkgs
pkgs.guile-fibers
Concurrent ML-like concurrency for Guile
pkgs.ocamlPackages.fiber
Structured concurrency library