Internal response disclosure via unguarded OAuth2 token exchange
Published Aug 20, 2026 · Updated Aug 20, 2026
SSRF in n8n before 1.123.69, 2.33.4, and 2.34.1 allows remote authenticated users to read internal responses via OAuth2. The access-token exchange uses a separate HTTP client without the SSRF guard applied to discovery and registration requests. Credential-creation permission and a completed OAuth2 flow are required, and disclosure is limited to responses produced for the fixed-shape token POST.
Summary
What happened
SSRF in n8n before 1.123.69, 2.33.4, and 2.34.1 allows remote authenticated users to read internal responses via OAuth2. The access-token exchange uses a separate HTTP client without the SSRF guard applied to discovery and registration requests. Credential-creation permission and a completed OAuth2 flow are required, and disclosure is limited to responses produced for the fixed-shape token POST.
The record
- CVE
- CVE-2026-77069
- Published
- Aug 20, 2026
- Updated
- Aug 20, 2026
- Vendor
- n8n
- Product
- n8n
- Classifications
- CWE-918
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 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 <1.123.69
- Affected versionversion=0 <2.33.4
- Affected versionversion=0 <2.34.1
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