Skip to main content
VulnerabilityPublished

CVE-2025-7578: Teledyne FLIR FB-Series O · Command Injection

Affects Teledyne FLIR FB-Series OSource CVE Database V5

0

Not known to be exploited · CVSS 2.3 Low.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.3% chance of exploitation in 30 days – higher than 71% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Teledyne FLIR FB-Series OAffected
  • =1.3.2.16
Fixed in–

AI-suggested

  1. Immediate assessment of the deployment of affected Teledyne FLIR FB-Series O and FH-Series devices within the organization is essential. Identify all devices running firmware version 1.3.2.16.
  2. Verify the current CGI server configuration to ensure that the vulnerable sendCommand functionality remains disabled. Avoid any changes that might enable this functionality inadvertently.
  3. Implement network segmentation and strict access controls to limit remote access to these devices, reducing the attack surface.
  4. Monitor device logs and network traffic for unusual command execution attempts or anomalies that could indicate exploitation attempts.
  5. Engage with Teledyne support channels persistently to request patches or official guidance, documenting all communications.
  6. Consider deploying compensating controls such as Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with custom rules to detect and block suspicious command injection patterns targeting these devices.
  7. Plan for firmware upgrades or device replacement if and when a patch becomes available.
  8. Educate operational technology (OT) and security teams about this vulnerability and the importance of maintaining current configurations and monitoring.

Description

A vulnerability was found in Teledyne FLIR FB-Series O and FLIR FH-Series ID 1.3.2.16. It has been declared as critical. This vulnerability affects the function sendCommand of the file runcmd.sh. The manipulation of the argument cmd leads to command injection. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The researcher highlights, that "[a]lthough this functionality is currently disabled due to server CGI configuration errors, it is essentially a 'time bomb' waiting to be activated". The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…