CVE-2025-6266VulnerabilityPublished 19 Jun 2025Updated 15 Oct 2025

CVE-2025-6266: Teledyne FLIR AX8 · Unrestricted Upload

Affects Teledyne FLIR AX8Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 1.49.16 : update Teledyne FLIR AX8 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.49.16

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Teledyne FLIR AX8	Affected =1.0 =1.1 =1.2 =1.3 =1.4 =1.5 =1.6 =1.7 =1.8 =1.9 =1.10 =1.11 =1.12 =1.13 =1.14 =1.15 =1.16 =1.17 =1.18 =1.19 =1.20 =1.21 =1.22 =1.23 =1.24 =1.25 =1.26 =1.27 =1.28 =1.29 =1.30 =1.31 =1.32 =1.33 =1.34 =1.35 =1.36 =1.37 =1.38 =1.39 =1.40 =1.41 =1.42 =1.43 =1.44 =1.45 =1.46 <=1.46	Fixed in–

AI-suggested

1. Immediately upgrade all Teledyne FLIR AX8 devices to firmware version 1.49.16 or later, as provided by the vendor, to remediate the unrestricted upload vulnerability. 2. Restrict network access to the device management interfaces by implementing network segmentation and firewall rules, ensuring that only authorized personnel and systems can reach the /upload.php endpoint. 3. Employ strong authentication and access control mechanisms on device management portals to prevent unauthorized access. 4. Monitor network traffic for unusual upload activity or attempts to access the /upload.php endpoint, using intrusion detection/prevention systems tailored for industrial control systems. 5. Conduct regular security audits and vulnerability assessments on operational technology devices to identify and remediate similar issues proactively. 6. Where possible, isolate FLIR AX8 devices from direct internet exposure and use VPNs or secure tunnels for remote management. 7. Maintain an inventory of all deployed FLIR AX8 devices and verify firmware versions to ensure timely patching. 8. Educate operational technology and security teams about the risks associated with device vulnerabilities and the importance of timely updates.

Description

A vulnerability was detected in Teledyne FLIR AX8 up to 1.46. Affected by this vulnerability is an unknown functionality of the file /upload.php. Performing manipulation of the argument File results in unrestricted upload. It is possible to initiate the attack remotely. The exploit is now public and may be used. Upgrading to version 1.49.16 addresses this issue. Upgrading the affected component is recommended. The vendor points out: "FLIR AX8 internal web site has been refactored to be able to handle the reported vulnerabilities."

Impact

For European organizations, the impact of this vulnerability can be substantial, especially for those in sectors such as energy, manufacturing, transportation, and critical infrastructure where FLIR AX8 devices are deployed for thermal monitoring and safety. Exploitation could allow attackers to upload malicious payloads, potentially leading to unauthorized access, data leakage, manipulation of sensor data, or denial of service conditions. This could disrupt operational technology environments, cause safety hazards, or facilitate lateral movement within networks. Given the device's role in monitoring physical environments, compromise could also affect physical security and safety systems. The medium severity rating reflects a moderate but tangible risk, particularly in environments where these devices are internet-facing or insufficiently segmented. The availability of public exploit code increases the urgency for European entities to address this vulnerability promptly to prevent targeted attacks or opportunistic exploitation.

Summary

CVE-2025-6266 is an unrestricted file upload vulnerability found in Teledyne FLIR AX8 thermal imaging cameras running firmware versions up to 1.46. The vulnerability resides in the /upload.php functionality, where the 'File' parameter is insufficiently validated, allowing an attacker to remotely upload arbitrary files without requiring authentication or user interaction. This flaw enables attackers to potentially execute malicious code, alter device configurations, or disrupt device operations, impacting confidentiality, integrity, and availability. The vulnerability is remotely exploitable over the network with low attack complexity and no privileges required, though the CVSS vector indicates a low scope and partial impact on confidentiality, integrity, and availability. The vendor has released version 1.49.16, which refactors the internal web interface to remediate this issue. No known exploits are currently reported in the wild, but public exploit code availability increases the risk of exploitation. The affected device, FLIR AX8, is commonly used in industrial monitoring, building automation, and critical infrastructure environments, making this vulnerability a significant concern for organizations relying on these devices for operational safety and security.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Oct 2025, 13:41 UTC

Technical details

References

Community reviews

Related threats