CVE-2026-67367: A vulnerability has been identified in SIMOVE Fleetmanager V3.1 (All versions < V3.1.13), SIMOVE Fleetmanag...
A vulnerability has been identified in SIMOVE Fleetmanager V3.1 (All versions < V3.1.13), SIMOVE Fleetmanager V3.2 (All versions < V3.2.4), SIMOVE Fleetmanager V3.3 (All versions < V3.3.2), SIMOVE Fleetmanager V4.0 (All versions < V4.0.1), SIPLANT V1.7 (All versions), SIPLANT V2.2 (All versions), SIPLANT V3.0 (All versions), SIPLANT V3.1 (All versions < V3.1.4). Affected devices do not properly validate and neutralize directory traversal sequences in the file-serving endpoint of the embedded HTTP server. This could allow an unauthenticated remote attacker to read arbitrary files from the underlying operating system without any credentials, potentially exposing sensitive data such as credential stores, private keys, and configuration secrets.
Security readout for executives and security teams
Plain-English summary
Affected Siemens SIMOVE Fleetmanager and SIPLANT systems can expose files from their underlying operating system to an unauthenticated remote attacker. Stolen files could include credentials, private keys, and configuration secrets, potentially enabling broader compromise. The issue is remotely reachable through the embedded web server and requires no user interaction.
Executive priority
Treat internet-accessible or broadly reachable affected systems as an immediate remediation priority. Patch supported branches, isolate systems lacking a named fixed release, and investigate possible secret exposure. Even without confirmed active exploitation, successful abuse could disclose credentials or private keys that enable wider operational compromise.
Technical view
CVE-2026-67367 is a CWE-23 directory traversal flaw in the embedded HTTP server’s file-serving endpoint. Improper validation and neutralization of traversal sequences permits unauthenticated arbitrary file reads. CVSS 4.0 rates it 9.2 because exploitation is network-accessible, low complexity, credential-free, and can cause high confidentiality impact without directly affecting integrity or availability.
Likely exposure
Exposure exists where an affected device’s embedded HTTP service is reachable by untrusted clients or compromised internal systems. Affected releases include SIMOVE Fleetmanager versions below specified fixed releases and all listed SIPLANT V1.7, V2.2, and V3.0 versions. The bundle provides no deployment prevalence or internet-exposure data.
Exploitation context
The source bundle does not report active exploitation, and the CVE is not identified as being in KEV. Nevertheless, unauthenticated network access, low attack complexity, and potentially sensitive file disclosure make exposed systems attractive targets. No public proof-of-concept status is established by the supplied evidence.
Researcher notes
The affected endpoint fails to neutralize directory traversal sequences, enabling arbitrary operating-system file reads without authentication. The supplied CVSS vector indicates confidentiality impact only, including subsequent-system confidentiality impact; it does not establish direct modification or denial of service. Testing should remain authorized and non-destructive. Exact endpoint details, indicators, and branch-specific workarounds are not included in the bundle.
Mitigation direction
Upgrade SIMOVE Fleetmanager to V3.1.13, V3.2.4, V3.3.2, or V4.0.1, as applicable.
Upgrade SIPLANT V3.1 to V3.1.4 or later.
For affected SIPLANT branches without a named fixed release, obtain current remediation guidance from Siemens.
Restrict embedded HTTP access to explicitly authorized management systems and trusted network segments.
Review potentially exposed credentials, private keys, and secrets; rotate them when disclosure cannot be excluded.
Validation and detection
Inventory SIMOVE Fleetmanager and SIPLANT deployments, recording product branch and exact installed version.
Confirm upgraded versions meet or exceed the fixed releases identified in the advisory.
Verify firewall and segmentation controls prevent untrusted access to each embedded HTTP service.
Review HTTP and security logs for unusual file requests or suspected traversal activity.
Check whether sensitive files were accessible, then assess related credentials and keys for possible exposure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-23: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection 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.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-23 · source CWE mapping
Relative Path Traversal
Relative Path Traversal represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.