cve.bz

CVE-2025-66630 gofiber fiber

9.2 criticalEPSS 0.5%Fix available

Critical (9.2) in gofiber fiber. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/gofiber/fiber/v2 2.52.11.

On this page
Fiber is an Express inspired web framework written in Go. Before 2.52.11, on Go versions prior to 1.24, the underlying crypto/rand implementation can return an error if secure randomness cannot be obtained. Because no error is returned by the Fiber v2 UUID functions, application code may unknowingly rely on predictable, repeated, or low-entropy identifiers in security-critical pathways. This is especially impactful because many Fiber v2 middleware components (session middleware, CSRF, rate limiting, request-ID generation, etc.) default to using utils.UUIDv4(). This vulnerability is fixed in 2.52.11.

Severity

CVSS 4.0

9.2 critical
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

9.4 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-02-10. 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-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
OWASP Top 10
A04:2025 Cryptographic Failures
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-66630 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-66630?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-66630?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-66630 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.11

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-68rr-p4fp-j59vGogithub.com/gofiber/fiber/v2<2.52.112.52.11
GO-2026-4471Gogithub.com/gofiber/fiberall versionsno fix published
GO-2026-4471Gogithub.com/gofiber/fiber/v2<2.52.112.52.11

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 15.6govulncheck-vulndb0.0.20260226T182644-150000.1.149.1SUSE-SU-2026:0757-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-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: openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is classified as Important rather than Critical because exploitation depends on an environmental failure of the randomness source rather than a condition directly controllable by a remote attacker. The flaw does not enable immediate unauthenticated remote code execution or direct system compromise; instead, impact occurs only if crypto/rand fails and the application subsequently relies on predictable UUID values in security-sensitive contexts. Since triggering conditions typically involve misconfigured containers, restricted environments, or degraded entropy sources, successful exploitation requires additional environmental or application-specific weaknesses. Therefore, while confidentiality and integrity can be significantly affected once triggered, the lack of a direct, easily exploitable remote attack path aligns the issue with Important severity rather than Critical.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-66630.

References

Check your stackJSON