Skip to main content
CVE-2025-54801VulnerabilityPublished Updated

CVE-2025-54801: gofiber fiber · Excessive Memory Allocation

Affects gofiber fiberSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High : upgrade to 2.52.9 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.52.9
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 2025

  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 2026-10-25.

What to do

Upgrade gofiber fiber to 2.52.9.

Affected software

ProductAffectedFixed in
gofiber fiberAffected
  • <2.52.9
Fixed in
  • 2.52.9

AI-suggested

1. Immediate upgrade of Fiber to version 2.52.9 or later, where the vulnerability is fixed. 2. Implement input validation and rate limiting at the application or web server level to detect and block unusually large numeric keys or suspicious form data patterns before they reach the Fiber BodyParser. 3. Employ Web Application Firewalls (WAFs) with custom rules to identify and mitigate attempts to exploit this vulnerability by filtering out requests with excessively large slice indices. 4. Monitor application logs for repeated crashes or panic events related to BodyParser usage to detect potential exploitation attempts early. 5. Conduct code reviews and testing to ensure that other parts of the application do not suffer from similar unchecked memory allocations. 6. For critical systems, consider deploying runtime protection tools that can detect and prevent abnormal memory allocation patterns. 7. Educate developers and DevOps teams about this vulnerability and the importance of timely dependency updates and secure parsing practices.

Description

Fiber is an Express inspired web framework written in Go. In versions 2.52.8 and below, when using Fiber's Ctx.BodyParser to parse form data containing a large numeric key that represents a slice index (e.g., test.18446744073704), the application crashes due to an out-of-bounds slice allocation in the underlying schema decoder. The root cause is that the decoder attempts to allocate a slice of length idx + 1 without validating whether the index is within a safe or reasonable range. If the idx is excessively large, this leads to an integer overflow or memory exhaustion, causing a panic or crash. This is fixed in version 2.52.9.

References

Community reviews

Loading reviews…