Security readout for executives and security teams
Plain-English summary
CVE-2026-22718 is a command injection vulnerability in the Spring CLI VSCode Extension. The provided source bundle states that versions 0.9.0 and older are affected, and successful exploitation can result in command execution on the user's machine.
Executive priority
Medium priority. The issue is not described as remotely exploitable or actively exploited in the provided bundle, but command execution on developer workstations can be high impact where those systems hold credentials or source access.
Technical view
The vulnerability is classified as CWE-78 command injection. The CVSS v3.1 score is 6.8 with vector CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L, indicating local attack vector, low attack complexity, low privileges required, required user interaction, unchanged scope, high confidentiality and integrity impact, and low availability impact.
Likely exposure
Exposure is most likely limited to developer workstations or managed endpoints where the Spring CLI VSCode Extension version 0.9.0 or older is installed and enabled. The bundle does not indicate exposure for servers or systems without this VSCode extension.
Exploitation context
The bundle does not support a claim of active exploitation: KEV is false and no included source states exploitation in the wild. Exploitation requires local context, low privileges, and user interaction, and may lead to command execution on the affected user's machine.
Researcher notes
No exploit details, proof of concept, or fixed version are provided in the source bundle. Do not claim active exploitation unless later vendor, KEV, or other authoritative evidence supports it. Treat versions 0.9.0 and older as affected based on the bundle.
Mitigation direction
- Inventory VSCode installations for the Spring CLI VSCode Extension and identify any versions 0.9.0 or older.
- Disable or uninstall affected extension versions until vendor guidance confirms a safe version or remediation path.
- Check the Spring advisory and official extension distribution channel for the vendor-confirmed fixed version before upgrading or re-enabling the extension.
- Prioritize remediation on developer machines with access to source code, credentials, CI/CD systems, or production infrastructure.
Validation and detection
- Confirm whether the Spring CLI VSCode Extension is installed on developer endpoints.
- Confirm the installed extension version and flag version 0.9.0 or older as affected.
- Verify that affected versions are disabled, removed, or updated according to vendor guidance.
- Review endpoint security telemetry for unusual local command execution associated with VSCode or the Spring CLI extension, without assuming compromise solely from installation.
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-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-22718 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
- Medium
- CVSS
- 6.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
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.
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:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L1.35.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.8MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://spring.io/security/cve-2026-22718CVE reference
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.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.