Security readout for executives and security teams
Plain-English summary
JetLinks Community 2.11 reportedly contains a critical server-side request forgery flaw in its device property-metadata import interface. An unauthenticated remote attacker may be able to make the server send unintended requests, potentially exposing sensitive information or enabling unauthorized changes. The supplied sources do not identify a vendor patch.
Executive priority
Treat this as an urgent exposure-review item. Prioritize internet-facing or broadly accessible JetLinks Community 2.11 systems, restrict access immediately where practical, and seek vendor remediation guidance. There is no supplied evidence of active exploitation, but the remote unauthenticated attack profile warrants prompt action.
Technical view
CVE-2026-75340 affects /device/instance/{productId}/property-metadata/import and is classified as CWE-918. Its CVSS 3.1 score is 9.1, with network access, low complexity, no privileges, and no user interaction. The vector rates confidentiality and integrity impact high, availability impact none.
Likely exposure
Exposure is most likely where JetLinks Community 2.11 is deployed and the affected import interface is reachable by untrusted users or networks. The structured affected-product fields are listed as unavailable, so broader version scope cannot be established from this bundle.
Exploitation context
The supplied bundle does not establish active exploitation, and the CVE is not identified as present in KEV. The scoring indicates remote, unauthenticated exploitation with low complexity, but the available evidence does not establish observed attacks, public weaponization, or reliable exploitation outcomes.
Researcher notes
The description specifically names JetLinks Community 2.11, while the structured affected vendor, product, and version fields contain only “n/a.” This inconsistency limits scope confidence. The sole vulnerability-specific reference is a GitHub report; the bundle provides no named patch, advisory, exploitation telemetry, or confirmed affected-version range beyond 2.11.
Mitigation direction
- Check JetLinks vendor guidance for an official fix or confirmed unaffected release.
- Restrict the affected import interface to trusted administrators and networks.
- Apply outbound request controls limiting access from the application to untrusted or sensitive destinations.
- Monitor the application for unexpected metadata imports and unusual outbound connections.
Validation and detection
- Inventory JetLinks deployments and confirm whether version 2.11 is present.
- Determine whether the affected interface is reachable without authentication or from untrusted networks.
- Review request logs for unusual access to the property-metadata import path.
- Review outbound connection logs for unexpected destinations originating from JetLinks.
- Confirm remediation status against current JetLinks vendor guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-75340 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/fangtang7/CVE/blob/main/jetlinks-community/ssrf.mdCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.