Resource exhaustion via unthrottled API documentation generation
Published Oct 15, 2026 · Updated Oct 15, 2026
Resource exhaustion in Lychee before 7.7.0 allows remote attackers to consume server CPU via repeated requests to /docs/api. The Scramble route in config/scramble.php uses only web middleware, with RestrictedDocsAccess disabled and no throttling; schema regeneration is inferred from response latency. After installation, the route needs no login; documented consequences are CPU consumption and API-schema exposure, not a demonstrated crash.
Summary
What happened
Resource exhaustion in Lychee before 7.7.0 allows remote attackers to consume server CPU via repeated requests to /docs/api. The Scramble route in config/scramble.php uses only web middleware, with RestrictedDocsAccess disabled and no throttling; schema regeneration is inferred from response latency. After installation, the route needs no login; documented consequences are CPU consumption and API-schema exposure, not a demonstrated crash.
The record
- CVE
- CVE-2026-77468
- Published
- Oct 15, 2026
- Updated
- Oct 15, 2026
- Vendor
- LycheeOrg
- Product
- Lychee
- Classifications
- CWE-770, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 15, 2026CVE publishedPublication date reported by the CVE source.
- Oct 15, 2026Record 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=< 7.7.0
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started