cve.bz

CVE-2025-54801 gofiber fiber

8.7 highEPSS 0.4%Fix available

High (8.7) in gofiber fiber. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/gofiber/fiber/v2 2.52.9.

On this page
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.

Severity

CVSS 4.0

8.7 high
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

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2025-08-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-789 Memory Allocation with Excessive Size Value
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-54801 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-54801?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-54801?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-54801 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
gofiber:fiberbefore 2.52.9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qx2q-88mx-vhg7Gogithub.com/gofiber/fiber/v2<2.52.92.52.9
GO-2025-3845Gogithub.com/gofiber/fiber/v2<2.52.92.52.9

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Module for Package Hub 15 SP6govulncheck-vulndb0.0.20250814T182633-150000.1.98.1SUSE-SU-2025:02912-1
openSUSELeap 15.6govulncheck-vulndb0.0.20250814T182633-150000.1.98.1SUSE-SU-2025:02912-1
openSUSETumbleweedgovulncheck-vulndb0.0.20250811T192933-1.1openSUSE-SU-2025:15434-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

References

Check your stackJSON