Predictable identifiers via silent randomness failure
Published Dec 9, 2025 · Updated Dec 9, 2025
Cryptographic failure in GoFiber Fiber Utils 1.1.0 and earlier and v2 before 2.0.0-rc.4 allows attackers to obtain predictable UUIDs. UUIDv4 falls back to UUID after uuid.NewRandom fails, while UUID ignores crypto/rand seeding failure and silently returns an all-zero identifier. The behavior requires Go before 1.24 and failed system randomness; security-critical use exposes sessions or tokens to collision, replay, or hijacking.
Summary
What happened
Cryptographic failure in GoFiber Fiber Utils 1.1.0 and earlier and v2 before 2.0.0-rc.4 allows attackers to obtain predictable UUIDs. UUIDv4 falls back to UUID after uuid.NewRandom fails, while UUID ignores crypto/rand seeding failure and silently returns an all-zero identifier. The behavior requires Go before 1.24 and failed system randomness; security-critical use exposes sessions or tokens to collision, replay, or hijacking.
The record
- CVE
- CVE-2025-66565
- Published
- Dec 9, 2025
- Updated
- Dec 9, 2025
- Vendor
- GoFiber
- Product
- Fiber Utils
- Classifications
- CWE-252, CWE-338, CWE-331, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- Dec 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=github.com/gofiber/utils <= 1.2.0
- Affected versionversion=github.com/gofiber/utils/v2 < 2.0.0-rc.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo