Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-63088 – SSRF via DNS Blocklist Bypass – StoatChat (revolt-january before 0.14.0)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-63088 is a Server-Side Request Forgery (SSRF) vulnerability in StoatChat’s revolt-january backend component, affecting all versions prior to 0.14.0. The flaw allows unauthenticated, network-accessible attackers to bypass the platform’s DNS-based IP blocklist and issue HTTP requests to internal-only hosts, including loopback and RFC1918 addresses. The vulnerability carries a CVSS v3.1 score of 8.6 (High).

Technical details

  • Root cause: The url_is_blacklisted function inspects only the first resolved DNS address for a given hostname (via resolved_ip.next()), while the underlying reqwest HTTP client receives a custom resolver that returns every resolved address and iterates through them in order, attempting each until one succeeds.
  • Trigger condition: An attacker who controls DNS for a hostname publishes two A records — a reachable public IP (which passes the blocklist check) followed by a loopback or internal IP (which is never validated). When reqwest fails to connect to the public address, it silently falls through to the internal address.
  • Attack vector: Unauthenticated HTTP GET requests to the /proxy or /embed endpoints, both of which accept a url parameter and require no authentication. The authentication extractor on /embed is commented out in the affected versions.
  • Impact: An unauthenticated remote attacker can cause the revolt-january service to issue HTTP GET requests to internal-only hosts (loopback, RFC1918, link-local), enabling reconnaissance and potential data exfiltration from services running on the internal network.

Affected software

  • StoatChat (revolt-january) — all versions prior to 0.14.0

Severity

CVSS v3.1 Base Score: 8.6 (High)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade revolt-january to version 0.14.0 or later, which addresses the incomplete address validation in the url_is_blacklisted function.
  • If immediate patching is not possible: Restrict network-level access to the /proxy and /embed endpoints via firewall rules or reverse-proxy ACLs so that only trusted clients can reach them, reducing unauthenticated exposure.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge