Service degradation via unbounded OIDC state allocation
Published Sep 4, 2026 · Updated Sep 9, 2026
Uncontrolled resource consumption in Forgekeep nebula-mesh 0.2.0 through 0.4.x allows remote attackers to degrade service via OIDC login requests. HandleLogin creates a fresh random state for every request, and rememberState retains each entry for ten minutes without a rate limit or live-state cap. OIDC must be enabled, but no credentials, identity-provider callback, or user interaction is required to cause application memory growth.
Summary
What happened
Uncontrolled resource consumption in Forgekeep nebula-mesh 0.2.0 through 0.4.x allows remote attackers to degrade service via OIDC login requests. HandleLogin creates a fresh random state for every request, and rememberState retains each entry for ten minutes without a rate limit or live-state cap. OIDC must be enabled, but no credentials, identity-provider callback, or user interaction is required to cause application memory growth.
The record
- CVE
- CVE-2026-55512
- Published
- Sep 4, 2026
- Updated
- Sep 9, 2026
- Vendor
- Forgekeep
- Product
- nebula-mesh
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 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.2.0, < 0.5.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.
Public exploit references
- GHSA-m3cx-mwpg-32jg safe local proof of conceptproof 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