CVE-2026-32133
Blind SSRF in 2FAuth Allows Internal Network Requests
Publication date: 2026-03-11
Last updated on: 2026-03-13
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| 2fauth | 2fauth | to 6.1.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a blind Server-Side Request Forgery (SSRF) issue in the 2FAuth web application, which manages Two-Factor Authentication accounts and generates security codes. Before version 6.1.0, authenticated users could exploit this flaw to make arbitrary HTTP requests from the server to internal networks and cloud metadata endpoints. The problem arises because the 'image' parameter in the OTP URL is not properly validated to block requests to internal or private IP addresses before the HTTP request is made. Although a previous fix ensured only valid images are stored by validating responses, the HTTP request itself still occurs before this validation, allowing the SSRF attack.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with authenticated access to the 2FAuth application to make unauthorized HTTP requests from the server to internal network resources or cloud metadata services. This could lead to unauthorized access to sensitive internal systems, exposure of confidential information, or manipulation of internal services that are not normally accessible externally.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed in version 6.1.0 of 2FAuth. Immediate mitigation involves upgrading the 2FAuth application to version 6.1.0 or later.