Quick answers
- Is CVE-2026-14983 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14983 being exploited in the wild.
- How severe is CVE-2026-14983?
- Informational severity, published 1 October 2026.
- Which products and versions are affected?
- Teledyne FLIR Aware2 through 6.9.0.2.
- Is there a fix for CVE-2026-14983?
- No fixed version is recorded yet. Customers should contact Teledyne at UGS-CHELMSFORD-TEAMS-FSE@Teledyne.com for updated software and remediation instructions. 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-14983 attacked?
- It is attacked from the adjacent network, in a network appliance.
- Am I affected by CVE-2026-14983?
- Check whether you run Teledyne FLIR Aware2 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.
How to fix
Customers should contact Teledyne at UGS-CHELMSFORD-TEAMS-FSE@Teledyne.com for updated software and remediation instructions.
Technical details
The vulnerability is a missing authentication check (CWE-306) in the PackBot web interface's reboot endpoint. An unauthenticated attacker with adjacent network access can send a simple HTTP GET request to trigger a system reboot; by scripting repeated requests, an attacker can trap the robot in a persistent reboot loop. The attack requires only network access to the robot's operational network and no authentication, user interaction, or special preconditions.
Affected products
- Teledyne FLIR Aware2 through 6.9.0.2
Timeline
- 2026-06-15: disclosed: Initial report to Teledyne
- 2026-10-01: advisory: Mandiant advisory published