CVE-2025-24523VulnerabilityPublished 12 Aug 2025Updated 13 Aug 2025

CVE-2025-24523: Edge Orchestrator software · Denial of Service

Affects Edge Orchestrator softwareSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium : upgrade to 24.11.1 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

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

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

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

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

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

Attack Vector: Adjacent: The vulnerable system is bound to a protocol stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone).
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: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within 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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Aug 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-25.

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

Upgrade Edge Orchestrator software to 24.11.1.

Affected software

Product	Affected	Fixed in
Edge Orchestrator software	Affected <24.11.1	Fixed in 24.11.1

AI-suggested

Organizations should prioritize upgrading the Edge Orchestrator software to version 24.11.1 or later as soon as it becomes available to remediate this vulnerability. If you cannot patch yet, network segmentation should be enforced to limit adjacent network access to the Edge Orchestrator components, restricting access to only trusted and authenticated users. Implement strict access controls and monitoring on edge orchestration interfaces to detect and prevent unauthorized or suspicious activities. Employ network-level protections such as firewalls and intrusion detection/prevention systems (IDS/IPS) to monitor and block anomalous traffic from adjacent networks. Additionally, conduct regular audits of user privileges to ensure that only necessary personnel have authenticated access to the orchestration software. Organizations should also prepare incident response plans specifically addressing potential DoS scenarios impacting edge orchestration to minimize downtime and operational impact.

Description

Protection mechanism failure for some Edge Orchestrator software before version 24.11.1 for Intel(R) Tiber(TM) Edge Platform may allow an authenticated user to potentially enable denial of service via adjacent access.

Impact

For European organizations leveraging Intel Tiber Edge Platform for edge computing—such as telecommunications providers, manufacturing plants, smart city infrastructure, and critical utilities—this vulnerability could lead to service interruptions. A denial of service in the Edge Orchestrator could halt orchestration and management of edge nodes, impacting real-time data processing and automation. This may degrade operational efficiency, delay critical decision-making, and increase downtime. Since the attack requires authenticated adjacent access with low privileges, insider threats or compromised local network segments pose a risk. The impact is primarily on availability, which could cascade into operational disruptions in sectors relying on edge computing for latency-sensitive applications. Given the growing adoption of edge platforms in Europe, especially in countries with advanced industrial and telecom sectors, this vulnerability could affect critical infrastructure and commercial deployments, potentially leading to financial losses and reputational damage.

References

intel.com/content/www/us/en/security-center/advisory/intel-sa-01317.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Aug 2025, 01:44 UTC

Technical details

References

Community reviews

Related threats