CVE-2026-53624

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
4.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
4.8
EG Score
4.8(medium)
EG Risk
—
EPSS
11.7%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 15, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_release, github, github_commit.
github Patch Available🟡 PoC Available

HSTS header never set in helmet middleware due to incorrect protocol check in gofiber/fiber · Advisory · gofiber/fiber · GitHub

https://github.com/gofiber/fiber/security/advisories/GHSA-gv83-gqw6-9j2c
github_release Patch Available

v3.4.0

Patch available: gofiber/fiber v3.4.0

https://github.com/gofiber/fiber/releases/tag/v3.4.0
github_pr Patch Available

🐛 bug: Use Scheme() for HTTPS detection and validate Helmet HSTS configuration

Patch available: gofiber/fiber v3.4.0 (PR #4389 merged 2026-06-02)

https://github.com/gofiber/fiber/pull/4389
github_commit Patch Available

commit 04dd4e7754f6 (gofiber/fiber)

Patch available: gofiber/fiber v3.4.0 (contains commit 04dd4e7754f6)

https://github.com/gofiber/fiber/commit/04dd4e7754f61768fddccacc79057e416f13e6bf

Vendor Advisories for CVE-2026-53624(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/gofiber/fiber—3.4.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-13 22:31 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-06 21:36 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53624?
CVE-2026-53624 is a medium vulnerability published on July 6, 2026. 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…
When was CVE-2026-53624 disclosed?
CVE-2026-53624 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53624 actively exploited?
CVE-2026-53624 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53624?
CVE-2026-53624 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-53624?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53624, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53624

Explore →

Is Your Infrastructure Affected by CVE-2026-53624?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs