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 90% 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.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.8MEDIUMmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity48% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
10th
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.
githubMentions a patch (unverified)🟡 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

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/gofiber/fiber—
  • every version up to 3.4.0: fixed in 3.4.0
—
github.com/gofiber/fiber/v3—
  • every version up to 3.4.0: fixed in 3.4.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 29× 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.

Showing the most recent 100 of 119 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-02 17:56 UTCEPSS rescore
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-29 15:22 UTCEPSS rescore
  13. 2026-09-28 13:51 UTCEPSS rescore
  14. 2026-09-28 13:41 UTCEG score recompute
  15. 2026-09-27 13:48 UTCEPSS rescore
  16. 2026-09-26 15:59 UTCEPSS rescore
  17. 2026-09-24 14:04 UTCEPSS rescore
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-23 06:22 UTCEG score recompute
  20. 2026-09-20 20:16 UTCEPSS rescore
  21. 2026-09-18 19:28 UTCEPSS rescore
  22. 2026-09-18 05:59 UTCEG score recompute
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-14 09:13 UTCEG score recompute
Show 75 more
  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-13 08:43 UTCEG score recompute
  3. 2026-09-12 03:51 UTCEG score recompute
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-10 09:35 UTCEPSS rescore
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-05 23:02 UTCEG score recompute
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-09-01 04:40 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 07:59 UTCEG score recompute
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 21:58 UTCEG score recompute
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-26 13:54 UTCEG score recompute
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 07:22 UTCEG score recompute
  24. 2026-08-22 05:48 UTCEG score recompute
  25. 2026-08-21 23:49 UTCEPSS rescore
  26. 2026-08-21 04:57 UTCEG score recompute
  27. 2026-08-20 22:55 UTCEPSS rescore
  28. 2026-08-20 04:26 UTCEG score recompute
  29. 2026-08-19 17:04 UTCEPSS rescore
  30. 2026-08-19 03:55 UTCEG score recompute
  31. 2026-08-18 13:48 UTCEPSS rescore
  32. 2026-08-18 03:08 UTCEG score recompute
  33. 2026-08-17 13:47 UTCEPSS rescore
  34. 2026-08-16 23:34 UTCEG score recompute
  35. 2026-08-16 14:56 UTCEPSS rescore
  36. 2026-08-16 02:14 UTCEPSS rescore
  37. 2026-08-15 23:04 UTCEG score recompute
  38. 2026-08-15 01:30 UTCEPSS rescore
  39. 2026-08-13 22:03 UTCEG score recompute
  40. 2026-08-13 22:00 UTCEPSS rescore
  41. 2026-08-12 21:33 UTCEG score recompute
  42. 2026-08-12 13:51 UTCEPSS rescore
  43. 2026-08-11 21:03 UTCEG score recompute
  44. 2026-08-11 00:00 UTCEPSS rescore
  45. 2026-08-09 20:02 UTCEG score recompute
  46. 2026-08-09 13:46 UTCEPSS rescore
  47. 2026-08-07 19:01 UTCEG score recompute
  48. 2026-08-06 18:31 UTCEG score recompute
  49. 2026-08-06 13:47 UTCEPSS rescore
  50. 2026-08-05 19:17 UTCEPSS rescore
  51. 2026-08-04 17:30 UTCEG score recompute
  52. 2026-08-04 15:10 UTCEPSS rescore
  53. 2026-08-04 10:39 UTCEPSS rescore
  54. 2026-08-03 16:59 UTCEG score recompute
  55. 2026-08-03 10:36 UTCEPSS rescore
  56. 2026-08-02 16:29 UTCEG score recompute
  57. 2026-08-02 02:27 UTCEPSS rescore
  58. 2026-08-01 15:59 UTCEG score recompute
  59. 2026-08-01 04:16 UTCEPSS rescore
  60. 2026-07-31 15:28 UTCEG score recompute
  61. 2026-07-30 16:28 UTCEPSS rescore
  62. 2026-07-30 14:52 UTCEG score recompute
  63. 2026-07-30 01:30 UTCEPSS rescore
  64. 2026-07-29 14:21 UTCEG score recompute
  65. 2026-07-28 15:37 UTCEPSS rescore
  66. 2026-07-28 13:51 UTCEG score recompute
  67. 2026-07-27 13:19 UTCEG score recompute
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-26 12:46 UTCEG score recompute
  70. 2026-07-25 14:18 UTCEPSS rescore
  71. 2026-07-24 14:18 UTCEPSS rescore
  72. 2026-07-23 14:18 UTCEPSS rescore
  73. 2026-07-23 03:19 UTCEG score recompute
  74. 2026-07-22 14:08 UTCEPSS rescore
  75. 2026-07-21 15:25 UTCEPSS rescore

Related CVEs(same product + 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 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 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53624?
CVE-2026-53624 has a CVSS base score of 4.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53624?
A fix for CVE-2026-53624 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53624 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs