# CVE-2026-53624: Fiber: HSTS header never set in helmet middleware due to incorrect protocol check

> Attackers can bypass HSTS protection in Fiber's helmet middleware because the header is never set, allowing potential protocol downgrade attacks.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-gv83-gqw6-9j2c, GO-2026-5912, MINI-6rv7-gfj9-hp3g, MINI-f7p5-wxxr-c3fg, UBUNTU-CVE-2026-53624

## What is CVE-2026-53624?

CVE-2026-53624 is a medium-severity vulnerability in gofiber fiber, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2026-53624?

3 open source packages ship an affected version, including github.com/gofiber/fiber and github.com/gofiber/fiber/v3. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gofiber/fiber` | Go | All versions | 3.4.0 |
| `github.com/gofiber/fiber` | Go | All versions | 3.4.0 |
| `github.com/gofiber/fiber/v3` | Go | All versions | 3.4.0 |

Products: Gofiber Fiber.

## How do I fix CVE-2026-53624?

Upgrade github.com/gofiber/fiber to 3.4.0 or later.

## Is CVE-2026-53624 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53624 exists.

## Other vulnerabilities in gofiber fiber

- [CVE-2024-38513](https://insights.sbomify.com/CVE-2024-38513/): Fiber Session Middleware Token Injection Vulnerability (critical 10.0)
- [CVE-2023-45128](https://insights.sbomify.com/CVE-2023-45128/): CSRF Token Reuse Vulnerability in fiber (critical 10.0)
- [CVE-2024-25124](https://insights.sbomify.com/CVE-2024-25124/): Fiber has Insecure CORS Configuration, Allowing Wildcard Origin with Credentials (critical 9.4)
- [CVE-2025-66630](https://insights.sbomify.com/CVE-2025-66630/): Fiber insecurely fallsback in utils.UUIDv4() / utils.UUID() — predictable / zero‑UUID on crypto/rand failure (critical 9.2)
- [CVE-2025-54801](https://insights.sbomify.com/CVE-2025-54801/): Fiber Susceptible to Crash via `BodyParser` Due to Unvalidated Large Slice Index in Decoder (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53624 and fix it if it is affected.

What it is: CVE-2026-53624 is a medium-severity vulnerability in gofiber fiber, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53624 exists.

Affected packages and fixed versions:
- github.com/gofiber/fiber (Go): affected all versions; fixed in 3.4.0
- github.com/gofiber/fiber (Go): affected all versions; fixed in 3.4.0
- github.com/gofiber/fiber/v3 (Go): affected all versions; fixed in 3.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53624/ (Markdown: https://insights.sbomify.com/CVE-2026-53624/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53624
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53624
- OSV: https://osv.dev/vulnerability/CVE-2026-53624

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53624/
Summaries are generated and may contain mistakes; the official description above is the record.