Unauthenticated service degradation via unbounded OAuth flows
Published Jun 18, 2026 · Updated Jun 18, 2026
Resource exhaustion in Hermes WebUI before 0.51.468 allows remote attackers to degrade service via unauthenticated OAuth-start requests. The OAuth start path creates pending flows and daemon polling workers without atomically checking and reserving provider/profile keys. Network access to the endpoint is sufficient; repeated or concurrent requests consume memory and threads and multiply upstream device-code requests.
Summary
What happened
Resource exhaustion in Hermes WebUI before 0.51.468 allows remote attackers to degrade service via unauthenticated OAuth-start requests. The OAuth start path creates pending flows and daemon polling workers without atomically checking and reserving provider/profile keys. Network access to the endpoint is sufficient; repeated or concurrent requests consume memory and threads and multiply upstream device-code requests.
The record
- CVE
- CVE-2026-55205
- Published
- Jun 18, 2026
- Updated
- Jun 18, 2026
- Vendor
- Nathan Esquenazi
- Product
- Hermes WebUI
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 18, 2026CVE publishedPublication date reported by the CVE source.
- Jun 18, 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=0 <0.51.468
What conditions does exploitation require?
What is affected?
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
- OAuth pending-flow resource-exhaustion reproducerproof of concept · demonstrated
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