CVE-2025-26472
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUncontrolled resource consumption 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn uncontrolled resource consumption vulnerability in Intel(R) Tiber(TM) Edge Platform's Edge Orchestrator software (versions before 24.11.1) allows an authenticated attacker with adjacent network access to cause denial of service by exhausting system resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Edge Orchestrator software versionCheck the installed version of Intel Tiber Edge Platform Edge Orchestrator software. This may be available through the software inventory, package manager, or by querying the service directly for its version information. Common locations include system package lists, Intel deployment tools, or service banner grabbing if the service exposes version details.Affected if The installed version is any version prior to 24.11.1 (e.g., 24.x versions below 24.11.1, or earlier major versions).
-
Verify adjacent network accessibilityDetermine if the Edge Orchestrator service is accessible from adjacent network segments. Check firewall rules, network ACLs, or service binding configurations that control whether the service port is exposed to network neighbors rather than being restricted to localhost or internal management networks.Affected if The Edge Orchestrator service port is reachable from adjacent network segments, allowing an attacker with adjacent network access to communicate with the service.
-
Confirm authentication mechanism statusReview whether local or network authentication for the Edge Orchestrator service is enabled and functional. Check if the service requires authentication for API or management interface access.Affected if Authentication is enabled but the service remains vulnerable to resource exhaustion attacks from an authenticated attacker.
You are affected if Edge Orchestrator software version is detected as lower than 24.11.1 AND the service is accessible from adjacent network segments to an authenticated attacker.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Edge Orchestrator software to version 24.11.1 or later to remediate the vulnerability.
24.11.1
- Identify the current version of Intel(R) Tiber(TM) Edge Platform Edge Orchestrator software
- Obtain version 24.11.1 or later from Intel's official support channels or download portal
- Apply the upgrade to the Edge Orchestrator software following Intel's standard upgrade procedures for the Tiber Edge Platform
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26472 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26472 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data