CVE-2025-22895
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 · uneditedExposure of sensitive information to an unauthorized actor for some Edge Orchestrator software for Intel(R) Tiber™ Edge Platform may allow an authenticated user to potentially enable information disclosure via local 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 · moderate confidenceThis is a local information disclosure vulnerability in Intel Tiber Edge Platform's Edge Orchestrator software. An authenticated user with local access can view sensitive information they should not have authorization to access, indicating inadequate role-based access controls or data segregation within the orchestrator component.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 installationLook for the Intel Tiber Edge Orchestrator service or process on the system. Check installed programs list or running services for 'Intel Tiber Edge' or 'Edge Orchestrator' components.Affected if Intel Tiber Edge Orchestrator software is present on the system
-
Determine Edge Orchestrator versionUse system inventory tools, software inventory commands, or check the application's About/Version information to obtain the installed version number of Edge Orchestrator.Affected if Version cannot be confirmed as post-fix or falls within an unknown vulnerable range (no specific version range provided in CVE)
-
Review role-based access control configurationAccess the Edge Orchestrator admin console or configuration files. Examine RBAC settings to determine if role permissions are properly defined and enforced for authenticated users.Affected if RBAC is not implemented, is misconfigured, or allows users to access data outside their defined role permissions
-
Verify user role assignments and data segregationCheck the user management section of Edge Orchestrator. Review which roles are assigned to local authenticated users and test whether users can access data or information outside their authorized scope.Affected if Authenticated local users can view sensitive information that should be restricted to other roles or user groups
-
Confirm local access requirementVerify that the vulnerability requires an authenticated user with local (physical or terminal) access to the system where Edge Orchestrator runs.Affected if Attacker has authenticated local access to the system hosting Edge Orchestrator
User is affected if Intel Tiber Edge Orchestrator is running, authenticated local users can access information outside their authorized role scope, and RBAC or data segregation controls are inadequate.
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.
From vendor dataImplement and enforce strict role-based access controls (RBAC) and proper data isolation between authenticated users in the Edge Orchestrator to ensure users can only access information explicitly authorized for their role.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22895 — 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-22895 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