dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-11346

MEDIUM · 5.3 CVSS v4.0 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Server-Side Request Forgery (SSRF) vulnerability in the custom process creation feature of linqi allows an authenticated attacker to probe internal network components. By crafting a specific process containing an HTTP Request component, an attacker can force the server to send arbitrary HTTP requests. By observing the varying application responses (Success, Failed, or 504 Gateway Time-out), the attacker can determine the status of internal ports, leading to internal network reconnaissance.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in linqi's custom process creation feature. An authenticated attacker can craft a process containing a malicious HTTP Request component that forces the server to send arbitrary HTTP requests to internal network resources. The attacker infers internal port status by analyzing application responses (Success, Failed, or 504 Gateway Timeout), enabling internal network reconnaissance.

MitigationImplement strict URL validation and allowlisting for the HTTP Request component in custom processes, restricting requests to approved external destinations only. Additionally, consider network segmentation and blocking of internal IP ranges (RFC 1918) from being reached by the application.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify linqi installation and version
    Locate the linqi application installation directory or check running services. Query the installed version using the application's version command, configuration file, or package manager information.
    Affected if linqi is installed and the version falls within the affected range (if known) or is an unpatched version of the product
  2. Verify custom process creation feature is enabled
    Inspect the linqi configuration files or admin settings to determine if the custom process creation feature is available and enabled for users.
    Affected if custom process creation feature is enabled and accessible to authenticated users
  3. Confirm HTTP Request component is available in custom processes
    Check the custom process builder/editor interface or configuration schema to see if an HTTP Request component/module is present and can be added to custom processes.
    Affected if the HTTP Request component exists and can be configured within custom processes
  4. Inspect URL validation settings for HTTP Request component
    Review the application's security configuration, admin settings, or custom process templates to determine whether URL validation or allowlisting is implemented for the HTTP Request component.
    Affected if no URL validation or allowlisting is configured, allowing arbitrary URLs to be specified
  5. Review network segmentation and internal IP blocking
    Examine the application's network configuration, firewall rules, or proxy settings to check if internal IP ranges (RFC 1918 addresses such as 10.x.x.x, 172.16-31.x.x, 192.168.x.x) and internal services are blocked from being reached by the HTTP Request component.
    Affected if internal network resources are reachable from the application's HTTP Request component and no restrictions are in place

A user is affected if linqi with the custom process creation feature is running, the HTTP Request component is available, and no URL validation or network blocking prevents the server from making arbitrary HTTP requests to internal resources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL validation and allowlisting for the HTTP Request component in custom processes, restricting requests to approved external destinations only. Additionally, consider network segmentation and blocking of internal IP ranges (RFC 1918) from being reached by the application.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11346 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11346 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data