EUVD-2026-66813
GHSA-pwh3-7crv-9wh2
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
SSRF via a device-management import endpoint most likely needs an authenticated session (PR:L); primary impact is confidentiality/relay (C:H) with limited integrity and no availability effect.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Lifecycle Timeline
4DescriptionCVE.org
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
AnalysisAI
Server-side request forgery in JetLinks Community 2.11 lets attackers abuse the device metadata import endpoint (/device/instance/{productId}/property-metadata/import) to coerce the server into issuing arbitrary outbound requests. Because the platform sits at the IoT control layer, this can be used to reach internal-only services, cloud metadata endpoints, and other network-segment resources normally shielded from the internet. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The attacker must be able to reach and invoke the specific endpoint /device/instance/{productId}/property-metadata/import on a JetLinks Community 2.11 instance and supply a metadata source (URL/reference) that the server dereferences server-side; a valid productId path value is needed. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The raw signals are split: CVSS 3.1 is 9.1 (AV:N/AC:L/PR:N/UI:N, C:H/I:H) and SSVC flags it automatable=yes with total technical impact, which argues for urgency, yet EPSS is only 0.14% (4th percentile) and there is no KEV listing, indicating no evidence of widespread exploitation despite a public POC. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who can reach the JetLinks management interface submits a device property-metadata import request whose metadata source points at an internal URL - for example the cloud instance-metadata service or an internal admin API. The JetLinks server fetches that URL and returns or acts on the response, letting the attacker read internal data or pivot to services unreachable from the internet. … |
| Remediation | No vendor-released patch identified at time of analysis - the available references are a third-party POC write-up, VulDB, and NVD, none citing a fixed release version, so upgrade guidance must be confirmed with the JetLinks project (github.com/jetlinks) before relying on it. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, immediately isolate all JetLinks Community 2.11 instances from internet-facing networks and deploy strict egress firewall rules restricting outbound connectivity to only essential endpoints; inventory all deployments and document current network exposure. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today