CVE-2025-22892
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 OpenVINO™ model server software maintained by Intel(R) before version 2024.4 may allow an unauthenticated 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 confidenceOpenVINO model server before version 2024.4 contains an uncontrolled resource consumption vulnerability allowing unauthenticated attackers 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 OpenVINO model server installationCheck if OpenVINO model server is present by looking for the ovms binary or Docker container. Common paths: /usr/bin/ovms, or run 'docker ps | grep openvino'Affected if OpenVINO model server is not installed - not affected. If present, continue to version check.
-
Determine installed versionRun 'ovms --version' or check the Docker image tag: 'docker images | grep openvino/model-server'Affected if Version is lower than 2024.4 - AFFECTED. Version 2024.4 or higher - NOT AFFECTED. Cannot determine version - assume potentially affected.
-
Verify network exposureCheck if the service listens on network interfaces. Inspect running configuration: 'docker ps --format "{{.Names}} {{.Ports}}" | grep ovms' or check config file for 'bind_bind' settingsAffected if Service is exposed to adjacent network (0.0.0.0 or accessible via IP) - attack surface exists. Localhost only - reduced risk but still potentially affected if local attackers exist.
-
Check resource limitsInspect Docker container resource limits: 'docker inspect <container_name> | grep -i Memory' or check systemd service limits if running nativelyAffected if No memory/CPU limits configured - vulnerable to resource exhaustion. Limits configured - may partially mitigate the issue.
If OpenVINO model server is installed with a version before 2024.4 and is network-accessible, the environment is likely affected by this denial of service vulnerability.
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 OpenVINO model server to version 2024.4 or later to obtain the patched release.
2024.4
- 1. Identify the current OpenVINO model server version by checking the installed package or container image tag
- 2. If running a version before 2024.4, plan for upgrade during a maintenance window
- 3. Backup current configuration files and any custom settings
- 4. For containerized deployments: Update the container image tag to use version 2024.4 or the latest stable release
- 5. For package-based installations: Download and install OpenVINO model server version 2024.4 from official Intel sources
- 6. Restore configuration files from backup
- 7. Verify the service starts successfully and validate that the vulnerability is resolved
- 8. Monitor system resources to confirm the uncontrolled resource consumption issue is mitigated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22892 — 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-22892 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