Is CVE-2026-6207 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-6207 being exploited in the wild.

How severe is CVE-2026-6207?

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-6207?

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-6207 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-6207?

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.

CVE-2026-6207: HAVELSAN Geographic Tracking System observable response discrepancy

CVE-2026-6207 · Severity: critical · CVSS 9.1 · Published 2026-06-05

A vulnerability has been identified in the HAVELSAN Geographic Tracking System, a platform used for monitoring and managing location-based data. The flaw allows unauthorized individuals to gain detailed information about the system's internal structure and configuration by observing differences in how the application responds to various requests. This information can be used to facilitate more advanced attacks, potentially leading to significant data exposure or unauthorized system access.

Technologies: HAVELSAN Geographic Tracking System. Vendors: HAVELSAN.

Quick answers

Is CVE-2026-6207 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-6207 being exploited in the wild.
How severe is CVE-2026-6207?: 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-6207?: 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-6207 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-6207?: 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

The HAVELSAN Geographic Tracking System is vulnerable to an observable response discrepancy (CWE-204). This occurs when the application provides different responses in a way that reveals internal state or configuration details to an unauthenticated remote attacker. By analyzing these discrepancies, an attacker can perform system footprinting to map out the environment. The vulnerability is rated critical with a CVSS score of 9.1, as it can lead to high confidentiality and integrity impacts. The issue is addressed in versions 0.0.2 and later.

Affected products

HAVELSAN Inc. Geographic Tracking System before v0.0.2

Timeline

2026-06-05: disclosed
2026-06-05: advisory

References

https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0325

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.