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

New CVE Detected

CVE-2026-92719 – SSRF via SQS queue_url – Quickwit through 0.9.0

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

Summary

CVE-2026-92719 is a Server-Side Request Forgery (SSRF) vulnerability affecting Quickwit, the open-source distributed search engine, through version 0.9.0. The flaw resides in the SQS file source configuration handling, where the queue_url parameter’s host and scheme are not validated, allowing an unauthenticated attacker to force a Quickwit node to issue requests to arbitrary internal addresses. The issue is rated High severity (CVSS 8.7).

Technical details

  • Root cause: The queue_url_endpoint() logic used to parse the queue_url parameter for SQS-backed sources relies on an overly permissive pattern that accepts any http(s)://host[:port] value without validating it against expected AWS SQS endpoints or blocking private/internal address ranges.
  • Trigger conditions: An attacker sends a request to the POST /api/v1/indexes/{index_id}/sources REST endpoint to create a new SQS file source, supplying a malicious queue_url pointing at an internal host or port. Affected code paths include the source resource handler, the index management connectivity check, and the SQS queue source’s endpoint extraction logic.
  • Attack vector: Network-based (AV:N), no privileges or user interaction required. Creating the source triggers a synchronous connectivity check that causes the node to make an outbound HTTP(S) request to the attacker-supplied endpoint before any configuration is persisted.
  • Impact: An attacker can direct the Quickwit node to connect to arbitrary internal or otherwise unreachable hosts and ports. Differences in error responses (service parse errors for open ports, connection-refused for closed ports, timeouts for filtered hosts) allow the attacker to fingerprint and enumerate internal network services, effectively enabling internal network reconnaissance from an externally reachable Quickwit instance. The vulnerability affects builds where the sqs source feature is enabled, which is the default in official release builds.

Affected software

  • Quickwit (quickwit-oss/quickwit): all versions through 0.9.0 (builds with the SQS source feature enabled, the default for official releases)

Severity

  • CVSS v4.0 Base Score: 8.7 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Check the official Quickwit repository and release notes for a fixed version addressing this issue and upgrade as soon as a patched release is available.
  • If no patch is available:
    • Disable the SQS file source feature if it is not required, to remove the vulnerable code path from the running node.
    • Restrict which users/systems can call the index/source management API (POST /api/v1/indexes/{index_id}/sources), since exploitation requires the ability to create a source.
    • Apply network-level egress filtering so the Quickwit node cannot reach internal management interfaces, cloud metadata endpoints, or other sensitive internal services.
    • Monitor outbound connection attempts from Quickwit nodes for requests to unexpected internal hosts/ports as an indicator of exploitation attempts.

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