# CVE-2025-22848: Denial of service in Edge Orchestrator software for Intel(R) Tiber™ Edge Platform

> An authenticated user can cause a denial of service in Intel Tiber Edge Platform via adjacent access due to improper condition checks.

- **Severity:** Medium 5.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:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2025
- **Updated:** 14 May 2025
- **Also known as:** GHSA-pw7w-9qc5-p77h

## What is CVE-2025-22848?

CVE-2025-22848 is a medium-severity denial of service vulnerability in Edge Orchestrator software for Intel(R) Tiber™ Edge Platform, published on 13 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper conditions check for some Edge Orchestrator software for Intel(R) Tiber™ Edge Platform may allow an authenticated user to potentially enable denial of service via adjacent access.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

## Which versions are affected by CVE-2025-22848?


## How do I fix CVE-2025-22848?

No fix has been published for CVE-2025-22848 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-22848 being exploited?

There is no known exploitation of CVE-2025-22848 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22848 and fix it if it is affected.

What it is: CVE-2025-22848 is a medium-severity denial of service vulnerability in Edge Orchestrator software for Intel(R) Tiber™ Edge Platform, published on 13 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-22848 in the wild and no public exploit code.

Affected product: Edge Orchestrator software for Intel(R) Tiber™ Edge Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-22848/ (Markdown: https://insights.sbomify.com/CVE-2025-22848/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22848
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22848
- OSV: https://osv.dev/vulnerability/CVE-2025-22848

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-22848/
Summaries are generated and may contain mistakes; the official description above is the record.