Skip to main content

elvix-sdk CVE-2026-108542

| EUVDEUVD-2026-96863 LOW
Server-Side Request Forgery (SSRF) (CWE-918)
2026-10-11 VulDB GHSA-524r-4mwx-jhpv
2.1
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with low-privilege access
  2. Delivery
    Craft malicious path argument
  3. Exploit
    Submit to MCP Request Handler
  4. Execution
    Server issues forged outbound request
  5. Impact
    Reach internal/restricted resource

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires low-privileged authenticated access to the MCP Request Handler exposed by src/mcp/index.ts in elvix-sdk versions up to and including 0.10.1; the attacker must be able to supply the 'path' argument that the handler uses to construct an outbound request. Exploitation is limited by the PR:L authentication requirement (not anonymous) and by the product's niche deployment - it is not a default-config unauthenticated internet-facing flaw. No user interaction is needed (UI:N), and no non-default configuration is indicated in the description beyond having the MCP request-handling feature in use.

Impact

This is a medium-severity SSRF (CWE-918) with real but constrained risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) indicates remote, low-complexity exploitation but requires low-level privileges (PR:L), so it is not a fully unauthenticated flaw. Vulnerable-system impact is uniformly Low (VC:L/VI:L/VA:L) with no subsequent-system impact (SC:N/SI:N/SA:N), consistent with a scope-limited SSRF rather than full compromise. The input carries E:P (Proof-of-Concept) and a public exploit reference, confirming publicly available exploit code exists - but there is NO CISA KEV listing and NO EPSS score provided, so active, widespread exploitation is NOT established. Signals are broadly consistent (medium score, PoC exists, authenticated-but-low barrier), with the main tempering factor being product obscurity: this is an SDK from an unknown vendor (021is), so despite public PoC the realistic attacker population and target footprint are small. Net: patch during normal cycles; not an emergency unless elvix-sdk is confirmed in your environment. Note the vendor did not respond to disclosure, so no official advisory or fixed version is confirmed.

Exploit ScenarioDerived

A low-privileged authenticated user sends a request to the MCP Request Handler (src/mcp/index.ts) with a crafted value in the 'path' argument, causing the server to issue an attacker-controlled outbound request. This can be used to reach internal services or cloud metadata endpoints otherwise unreachable from outside. A public proof-of-concept exploit exists, lowering the effort required to reproduce the attack.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 11, 2026

Server-side request forgery (SSRF) in elvix-sdk versions up to 0.10.1 allows remote attackers with low-privileged authenticated access to the MCP Request Handler to manipulate the 'path' argument in src/mcp/index.ts, causing the server to make arbitrary outbound requests. Publicly available exploit code exists, though no confirmed active exploitation has been observed. The vendor was contacted but did not respond, and no patch is available, leaving mitigation to compensating controls.

RemediationAI

No vendor-released patch is available at the time of analysis because the vendor did not respond to the disclosure. As a compensating control, disable the MCP Request Handler if its functionality is not essential; this removes the attack surface but may break MCP-dependent features. If the handler must be used, restrict outbound network traffic from the server to a strict allowlist of trusted destinations, which can prevent access to internal services but requires maintenance. Implement input validation on the 'path' argument to ensure it only contains expected values and does not allow arbitrary URLs or internal addresses; however, validation may be bypassed if not comprehensive. Enforce strict authentication and authorization, and limit access to the MCP Request Handler to only trusted, low-privileged users, since the vulnerability requires authenticated access. Monitor server logs for unusual outbound requests. Given the public exploit code (https://github.com/Xh1Xxhg/public_exp/issues/4), prioritize these mitigations.

Affected VersionsENISA

elvix-sdk 0.10.0
elvix-sdk 0.10.1

Affected Packages

euvd elvix_sdk no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is an instance of CWE-918 (Server-Side Request Forgery) in the MCP Request Handler component of elvix-sdk, specifically in the file src/mcp/index.ts. The MCP Request Handler processes requests that may involve making outbound HTTP requests, and it uses the 'path' argument to construct the target URL without sufficient validation. An attacker who can supply this argument can force the server to send requests to arbitrary internal or external systems, potentially accessing sensitive services or metadata endpoints. The CPE cpe:2.3:a:021is:elvix-sdk:*:*:*:*:*:*:*:* indicates that all versions are potentially affected, though the description specifies versions up to 0.10.1. The root cause is a failure to properly neutralize special elements in the outbound request, allowing an attacker to control the destination. The vulnerability requires authentication (PR:L) and remote network access (AV:N).

Know when Elvix Sdk gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
vuln.today AI 6.3 MEDIUM

Remote network vector with low complexity but a low-privilege auth barrier (PR:L), and SSRF yields limited, non-scope-changing impact so C/I/A are each Low.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
Oct 11, 2026 - 08:22 NVD
MEDIUM LOW
CVSS changed
Oct 11, 2026 - 08:22 NVD
5.3 (MEDIUM) 2.1 (LOW)
CVE Published
Oct 11, 2026 - 07:15 cve.org
MEDIUM 5.3

DescriptionCVE.org

A vulnerability was found in 021is elvix-sdk up to 0.10.1. Affected by this vulnerability is an unknown functionality of the file src/mcp/index.ts of the component MCP Request Handler. The manipulation of the argument path results in server-side request forgery. The attack can be executed remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Rare
obscure vendor (021is) SDK, no known enterprise footprint
Exploit
POC
Public exploit code exists
Social Media
2
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Low

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy