Quick answers
- Is CVE-2026-6209 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6209 being exploited in the wild.
- How severe is CVE-2026-6209?
- Critical severity, with a CVSS score of 9.1, published 5 June 2026.
- Which products and versions are affected?
- HAVELSAN Geographic Tracking System before v0.0.2.
- Is there a fix for CVE-2026-6209?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-6209 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-6209?
- Check whether you run HAVELSAN Geographic Tracking System at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A critical vulnerability exists in HAVELSAN Inc. Geographic Tracking System prior to version 0.0.2 due to improper access control (CWE-284) and missing authorization (CWE-862). The system fails to properly enforce Access Control Lists (ACLs) on certain functionalities. A remote, unauthenticated attacker can exploit this over the network with low complexity to access and execute restricted functions. This can result in high impacts to data confidentiality and integrity, as unauthorized users may view or manipulate tracking data. The issue is addressed in version 0.0.2.
Affected products
- HAVELSAN Inc. Geographic Tracking System before v0.0.2
Timeline
- 2026-06-05: disclosed
- 2026-06-05: advisory