Vulnerabilities in pkg:golang/github.com/gofiber/fiber
PACKAGECVE-2026-53624 is a MODERATE (CVSS 4.8) gofiber never set hsts header vulnerability (CWE-319: Cleartext Transmission of Sensitive Information) affecting Github.com/gofiber/fiber libraries in the Go ecosystem. The issue involves gofiber never set hsts header in helmet middleware due to incorrect protocol check. Remediation is available by upgrading affected packages to version 3.4.0.
pkg:golang/github.com/gofiber/fiber
Vulnerability advisories affecting package pkg:golang/github.com/gofiber/fiber. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-gv83-gqw6-9j2c | CVE-2026-53624 | MODERATE | GoFiber never set HSTS header in helmet middleware due to incorrect protocol check |
| GHSA-98j2-3j3p-fw2v | CVE-2024-38513 | CRITICAL | Session Middleware Token Injection Vulnerability |
| GHSA-3q5p-3558-364f | CVE-2023-41338 | MODERATE | Fiber unauthorized access vulnerability in `ctx.IsFromLocal()` |
| GHSA-9cx9-x2gp-9qvh | CVE-2020-15111 | MODERATE | CRLF vulnerability in Fiber |
CVE-2026-53624 at a Glance
Security Impact
CVSS: 4.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N).
How to Fix CVE-2026-53624
To remediate this vulnerability, upgrade all affected Github.com/gofiber/fiber dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/gofiber/fiber to 3.4.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/gofiber/fiber
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-53624, inspect your project dependencies for Github.com/gofiber/fiber:
inspect dependencies for github.com/gofiber/fiber
Analyze the terminal output to locate any version of Github.com/gofiber/fiber in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.4.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-319: Cleartext Transmission of Sensitive Information, where the product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. In Github.com/gofiber/fiber, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-53624 Affected Github.com/gofiber/fiber Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/gofiber/fiber
|
Go |
< 3.4.0
|
3.4.0
|
References
Frequently Asked Questions
What is CVE-2026-53624?
Which Github.com/gofiber/fiber versions are affected?
What version fixes CVE-2026-53624?
Is github.com/gofiber/fiber affected?
What is the CVSS score of CVE-2026-53624?
What CWE is associated with CVE-2026-53624?
How can I check Go dependencies for CVE-2026-53624?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-gv83-gqw6-9j2c",
"modified" : "2026-07-06T20:43:12Z",
"published" : "2026-07-06T20:43:12Z",
"aliases" : [ "CVE-2026-53624" ],
"summary" : "GoFiber never set HSTS header in helmet middleware due to incorrect protocol check",
"details" : "### Summary\n\nThe `helmet` middleware in gofiber/fiber never sets the `Strict-Transport-Security` (HSTS) response header, even when `HSTSMaxAge` is explicitly configured, because the condition check at `helmet.go:67` uses `c.Protocol()` — which returns the HTTP protocol version string (e.g., `\"HTTP/1.1\"`, `\"HTTP/2.0\"`) — instead of `c.Scheme()` — which returns the URL scheme (`\"http\"` or `\"https\"`). Since `c.Protocol()` never equals `\"https\"` in any real deployment, the HSTS header is permanently disabled, defeating the security protection.\n\n### Details\n\n**Root cause:** `middleware/helmet/helmet.go`, line 67:\n\n```go\nif c.Protocol() == \"https\" && cfg.HSTSMaxAge != 0 {\n```\n\n`c.Protocol()` (defined at `req.go:865-867`) delegates to `fasthttp.Request.Header.Protocol()`, which returns the HTTP protocol version:\n- `\"HTTP/1.1\"` for HTTP/1.1 connections\n- `\"HTTP/2.0\"` for HTTP/2 connections\n\nThe correct method is `c.Scheme()` (defined at `req.go:844-862`), which returns:\n- `\"http\"` for plain HTTP connections\n- `\"https\"` for TLS connections\n\nSince `\"HTTP/1.1\" != \"https\"` always evaluates to `true`, the entire HSTS block (lines 67-76) is dead code.\n\n**Note on test coverage:** The existing helmet test (`helmet_test.go`) passes because it uses `ctx.Request.Header.SetProtocol(\"https\")` to artificially force `Protocol()` to return `\"https\"`. However, `fasthttp.Request.Header.SetProtocol()` sets the HTTP version field, and real HTTP requests never have protocol `\"https\"` — they have `\"HTTP/1.1\"` or `\"HTTP/2.0\"`. The test is validating the wrong thing.\n\n### PoC\n\n**Clean-checkout maintainer-runnable recipe:**\n\n1. Save the following as `middleware/helmet/poc_hsts_test.go`:\n\n```go\npackage helmet\n\nimport (\n \"crypto/tls\"\n \"net/http/httptest\"\n \"testing\"\n\n \"github.com/gofiber/fiber/v3\"\n)\n\nfunc Test_PoC_HSTS_NeverSet(t *testing.T) {\n app := fiber.New()\n app.Use(New(Config{\n HSTSMaxAge: 31536000,\n }))\n app.Get(\"/\", func(c fiber.Ctx) error {\n return c.SendString(\"ok\")\n })\n\n // Simulate HTTPS connection\n req := httptest.NewRequest(fiber.MethodGet, \"/\", nil)\n req.TLS = &tls.ConnectionState{}\n\n resp, _ := app.Test(req)\n hsts := resp.Header.Get(\"Strict-Transport-Security\")\n\n if hsts == \"\" {\n t.Log(\"BUG CONFIRMED: HSTS header not set. c.Protocol() returns 'HTTP/1.1', not 'https'\")\n t.Log(\"Fix: change c.Protocol() == 'https' to c.Scheme() == 'https' on line 67\")\n }\n}\n```\n\n2. Run: `go test -run Test_PoC_HSTS_NeverSet -v ./middleware/helmet/`\n\n**Expected vulnerable output:**\n```\n=== RUN Test_PoC_HSTS_NeverSet\n BUG CONFIRMED: HSTS header not set. c.Protocol() returns 'HTTP/1.1', not 'https'\n Fix: change c.Protocol() == 'https' to c.Scheme() == 'https' on line 67\n--- PASS: Test_PoC_HSTS_NeverSet\n```\n\n**Expected output after fix:**\n```\n=== RUN Test_PoC_HSTS_NeverSet\n--- PASS: Test_PoC_HSTS_NeverSet\n (HSTS header is set: \"max-age=31536000; includeSubDomains\")\n```\n\n**Observed output from this environment (commit `ee98695f`):**\n```\n=== RUN Test_PoC_HSTS_NeverSet\n poc_hsts_test.go:39: HSTS header value: \"\"\n poc_hsts_test.go:42: BUG CONFIRMED: HSTS header is NOT set even over TLS\n poc_hsts_test.go:43: Root cause: helmet.go:67 uses c.Protocol() which returns HTTP version\n poc_hsts_test.go:44: c.Protocol() returns 'HTTP/1.1' not 'https'\n poc_hsts_test.go:45: Fix: use c.Scheme() == 'https' instead of c.Protocol() == 'https'\n--- PASS: Test_PoC_HSTS_NeverSet\n```\n\n**Negative/control case:** With `HSTSMaxAge: 0` (default), HSTS is correctly not set (this is expected behavior, not a bug).\n\n**Cleanup:** Remove `poc_hsts_test.go` after verification.\n\n### Impact\n\nThe HSTS header is never applied in production, leaving all users vulnerable to:\n- **SSL stripping attacks:** An active network attacker can downgrade HTTPS connections to HTTP, intercepting traffic between the client and server.\n- **Protocol downgrade:** Without HSTS, browsers will silently accept HTTP connections to the site, even if the site supports HTTPS.\n- **Cookie theft over HTTP:** Session cookies without the `Secure` flag will be sent over HTTP if the user is tricked into an HTTP connection.\n\nThis affects any application that:\n1. Uses the `helmet` middleware\n2. Configures `HSTSMaxAge > 0` expecting HSTS protection\n3. Serves traffic over HTTPS\n\nThe vulnerability requires an active MITM attacker on the network path, which is realistic in public Wi-Fi, corporate networks, and ISP-level scenarios.\n\n### Suggested remediation\n\nIn `middleware/helmet/helmet.go`, line 67, replace `c.Protocol()` with `c.Scheme()`:\n\n```go\n// Before (broken):\nif c.Protocol() == \"https\" && cfg.HSTSMaxAge != 0 {\n\n// After (fixed):\nif c.Scheme() == \"https\" && cfg.HSTSMaxAge != 0 {\n```\n\nAdditionally, update the existing test to use a realistic TLS simulation instead of `SetProtocol(\"https\")`:\n\n```go\n// Before (artificial - sets HTTP version to \"https\" which never happens in practice):\nctx.Request.Header.SetProtocol(\"https\")\n\n// After (realistic - simulates TLS connection):\nctx.RequestCtx().Request.Header.SetProtocol(\"HTTP/1.1\")\nctx.RequestCtx().TLS = &tls.ConnectionState{}\n```\n\n**Regression test:** Add a test case that verifies HSTS is set when `req.TLS` is non-nil and `HSTSMaxAge > 0`, without using `SetProtocol`.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/gofiber/fiber"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.4.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 3.3.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/gofiber/fiber/security/advisories/GHSA-gv83-gqw6-9j2c"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/gofiber/fiber"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-319" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-06T20:43:12Z",
"nvd_published_at" : null
}
}