Quick answers
- Is CVE-2026-55393 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55393 being exploited in the wild.
- How severe is CVE-2026-55393?
- Informational severity, published 1 October 2026.
- Which products and versions are affected?
- Teledyne FLIR Aware2 through 6.9.0.2 (PackBot) and 1.7.9 (FirstLook).
- Is there a fix for CVE-2026-55393?
- A patch was published on 2026-09-30: Updated software available from Teledyne Until you apply it: Contact Teledyne at UGS-CHELMSFORD-TEAMS-FSE@Teledyne.com for updated software and remediation instructions.</anigation> </invoke> Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55393 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-55393?
- 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
Contact Teledyne at UGS-CHELMSFORD-TEAMS-FSE@Teledyne.com for updated software and remediation instructions.</anigation> </invoke>
Technical details
A local file inclusion (path traversal) vulnerability exists in the web service due to insufficient input validation, allowing attackers to manipulate file paths via crafted requests. Remote unauthenticated attackers with network access can read arbitrary files on the robot system, including configurations, OS files, and credentials, which can be used to escalate privileges and achieve remote code execution.
Affected products
- Teledyne FLIR Aware2 through 6.9.0.2 (PackBot) and 1.7.9 (FirstLook)
Timeline
- 2026-03-31: disclosed: Initial report to Teledyne
- 2026-09-30: patched: Updated software available from Teledyne
- 2026-10-01: advisory: Mandiant advisory published