/

CVE-2026-92719

Severity:

HIGH RISK

(7.5)

SSRF (CWE-918) in Quickwit SQS File Source API Endpoint

CVE-2026-92719

Awaiting Analysis

Vulnerability type

Category:

Server-Side Request Forgery

CWE:

CWE-918

Impact:

Internal Network Discovery and Service Fingerprinting

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Quickwit through version 0.9.0 does not sufficiently validate the host and scheme supplied in the queue_url parameter for SQS file sources. An attacker who can access the source-creation API may cause a node to send requests to arbitrary internal addresses, enabling network discovery and service fingerprinting.

Affected context

The vulnerability occurs in Quickwit deployments that use SQS file sources and expose an API capable of creating or configuring those sources. It becomes risky when user-controlled queue_url values are accepted without strict validation of the destination host and scheme, and when the Quickwit node can reach internal or otherwise restricted network services.

Exploit preconditions

  • Attack surface: The create-source API or another interface that accepts SQS file-source configuration
  • Required access: Permission or access sufficient to submit a source definition
  • Trigger point: Processing the supplied queue_url while establishing or testing the SQS source
  • Why exploitation is possible: Host and scheme validation does not adequately constrain outbound requests, allowing attacker-influenced destinations and observable connection responses

Why this happens

The underlying issue is insufficient destination validation for a server-side request feature. The application treats a user-controlled queue URL as a trusted network destination without enforcing an appropriate allowlist or restricting supported schemes and hosts. This maps to CWE-918: Server-Side Request Forgery, where an application makes network requests on behalf of an attacker and may expose internal connectivity or service behavior.

Potential impact

  • Internal network addresses may be scanned from the Quickwit node
  • Restricted services may be fingerprinted through connection-response differences
  • Network topology and service exposure may be inferred
  • Requests may reach administrative or otherwise unintended internal endpoints
  • Availability or logging impact may occur on targeted internal services

General mitigation guidance

Mitigation generally focuses on reducing trust in destination URLs and limiting the network capabilities of the Quickwit process.

Common defensive patterns include:

  • Accepting only explicitly supported schemes and validating URLs with a strict parser
  • Restricting destination hosts to an approved SQS endpoint allowlist
  • Resolving hostnames and rejecting loopback, link-local, private, reserved, and otherwise disallowed address ranges
  • Rechecking resolved destinations to reduce DNS-rebinding exposure
  • Separating configuration submission from outbound network access where practical
  • Applying egress network policies and least-privilege service permissions
  • Avoiding detailed connection errors that reveal internal service behavior

How teams detect issues like this

Organizations commonly detect SSRF risks through:

  • Static analysis rules for outbound requests built from user-controlled URLs
  • Code review checks for missing scheme, host, redirect, and private-address validation
  • API policy enforcement requiring approved destination domains
  • Egress monitoring for unexpected connections to private, loopback, link-local, or metadata-service address ranges
  • Alerting on unusual source-creation activity and repeated connection failures across internal address ranges
  • Automated security review tools that identify unvalidated network destinations

Sources

SourceLink
github.comgithub.com/quickwit-oss/quickwit
github.comgithub.com/quickwit-oss/quickwit/blob/v0.9.0/quickwit/quickwit-indexing/src/source/queue_sources/sqs_queue.rs#L230-L243
github.comgithub.com/quickwit-oss/quickwit/blob/v0.9.0/quickwit/quickwit-serve/src/index_api/source_resource.rs#L56-L66
github.comgithub.com/quickwit-oss/quickwit/issues/6703
vulncheck.comvulncheck.com/advisories/quickwit-through-0.9.0-ssrf-via-sqs-queue-url-parameter

Frequently asked

questions

It may be exploitable through the create-source API when that interface is reachable by an attacker and permits the attacker to submit or influence SQS file-source configuration.

The attacker generally needs sufficient authorization to call the relevant API or otherwise create a source definition. The exact scope depends on the deployment's authentication and authorization controls.

Strictly allowlist supported schemes and destination hosts, reject private and special-use address ranges, and enforce outbound network restrictions as an additional control.

Treat all user-supplied URLs as untrusted, centralize destination validation, limit egress from application nodes, and monitor for unexpected internal network requests.

Find out what's already
exploitable in your codebase.