CVE-2026-27644
Traccar 6.11.1 – 6.13.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:LSummary
CVE-2026-27644 is a medium-severity Improper Neutralization of Formula Elements in a CSV File (CWE-1236) vulnerability in Traccar Traccar. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique User Execution (T1204); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-15 (Information Output Filtering) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-27306
Vulnerability Data
Traccar is an open source GPS tracking system. In versions between 6.11.1 and 6.13.0, the CSV export functionality writes position data, including user-controlled device and computed attributes, to CSV output without proper escaping. An attacker can inject spreadsheet formulas through…
more
exported fields. When a manager or administrator opens the exported CSV file in spreadsheet software, this can cause formula execution and lead to command execution or data exfiltration. This has been patched in version 6.13.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.10
Mitigating Controls (NIST 800-53 r5) AI
Output filtering/validation directly stops unneutralized formula elements from being written into CSV files.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require output neutralization for untrusted CSV content to block formula injection.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect formula injection but does not itself implement the mitigation.
Secure SDLC mandates input validation and output encoding that directly prevents formula injection in CSV exports.
Application security requirements include rules for safe CSV generation and handling of untrusted data.
Secure architecture principles encourage safe data export design but do not specifically address CSV formula neutralization.
Secure coding standards explicitly require neutralization of special characters when writing CSV files.