ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-41753

The object name of a dynamically created BACnet File Object is interpreted as a file path without sufficient validation.

Published Oct 1, 2026 · catalog updated Oct 14, 2026 · The object name of

Check if you run it

No confirmed exploitation is on record for CVE-2025-41753. EPSS is 0.59%. Act only if a listed version of The object name of is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The object name of).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.59%
Remediation
Not established
Affected products
See sources for product scope

The object name of a dynamically created BACnet File Object is interpreted as a file path without sufficient validation. Because relative paths are not limited to the intended directory, an unauthenticated remote attacker can traverse outside of it and read or overwrite arbitrary files on the device, which may lead to full system compromise.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2025-41753

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-41753. EPSS is 0.59%. Act only if a listed version of The object name of is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-22: Path Traversal. EPSS 0.59%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 1, 2026 · NIST NVD

    Detected

    The object name of a dynamically created BACnet File Object is interpreted as a file path without sufficient validation. Because relative paths are not limited to the intended directory, an unauthenticated remote attacker can traverse outside of it and read or overwrite arbitrary files on the device, which may lead to full system compromise.

  2. Oct 14, 2026 · NIST NVD

    Updated

    The object name of a dynamically created BACnet File Object is interpreted as a file path without sufficient validation. Because relative paths are not limited to the intended directory, an unauthenticated remote attacker can traverse outside of it and read or overwrite arbitrary files on the device, which may lead to full system compromise.

Sources

  • CVE.orgVulnerability recordCVE-2025-41753

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-41753

    30-day exploitation probability 0.6%

    first.org
  • NIST NVDVulnerability recordCVE-2025-41753

    The object name of a dynamically created BACnet File Object is interpreted as a file path without sufficient validation. Because relative paths are not limited to the intended directory, an unauthenticated remote attacker can traverse outside of it and read or overwrite arbitrary

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.