Skip to main content
VulnerabilityPublished

CVE-2026-53624: github.com/gofiber/fiber · GoFiber Never Set HSTS Header

Affects github.com/gofiber/fiberSource GCVE Database

0

Not known to be exploited · CVSS 4.8 Medium : upgrade to 3.4.0 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects
Go. prior to 3.4.0
Patch
Available – fixed in 3.4.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade github.com/gofiber/fiber to 3.4.0.

Affected software

ProductAffectedFixed in
Gogithub.com/gofiber/fiberAffected
  • <3.4.0
Fixed in
  • 3.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…