dbcve.org
OmniApplication · Siderolabs

CVE-2025-61688

HIGH · 7.5 CVSS v3.1 Published 2025-10-13
Fix available
A fix is available. Upgrade to 1.0.2 / 1.1.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Omni manages Kubernetes on bare metal, virtual machines, or in a cloud. Prior to 1.1.5 and 1.0.2, Omni might leak sensitive information via an API.

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 confidence

Omni is a Kubernetes management platform. Prior to versions 1.1.5 and 1.0.2, the product contains an information disclosure vulnerability where sensitive data may be leaked through its API endpoint. The CVSS 7.5 score indicates network-exploitable access with low or no authentication required and high confidentiality impact.

MitigationUpgrade Omni to version 1.1.5 or 1.0.2 to patch the information disclosure vulnerability. If immediate patching is not possible, restrict API access to trusted networks and monitor for unauthorized data access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OmniApplication
Affected:< 1.0.2>= 1.1.0, < 1.1.5

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Omni version
    Use the Omni CLI (omni --version) or check the Kubernetes deployment/daemonset version labels. On Siderolabs machines, check via `omnictl version` or inspect the Talos machine configuration for Omni version metadata.
    Affected if The installed version is less than 1.0.2, or greater than or equal to 1.1.0 but less than 1.1.5.
  2. Verify API endpoint accessibility
    Determine if the Omni API service (typically port 443 or 8080) is reachable from untrusted networks. Check Kubernetes service type, ingress configuration, and any network policies controlling access to the Omni API pod.
    Affected if The API endpoint is exposed to network segments that contain untrusted users or systems.
  3. Review API authentication settings
    Inspect Omni configuration for authentication enforcement on API endpoints. Check whether anonymous or unauthenticated access is permitted for sensitive API routes.
    Affected if Anonymous or weak authentication is enabled, allowing unauthenticated access to sensitive API endpoints.
  4. Audit API access logs for data exfiltration
    Review Omni API access logs for unusual patterns such as bulk data retrieval, access to user credentials, tokens, or configuration data from endpoints that should require elevated privileges.
    Affected if Logs show unexpected data access from unauthenticated or low-privilege API requests.

A user is affected if Omni version is less than 1.0.2 or between 1.1.0 and 1.1.5, AND the API is accessible from untrusted networks with weak or no authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.0.2 / 1.1.5 or later
Fixed in 1.0.21.1.5
Interim mitigation

Upgrade Omni to version 1.1.5 or 1.0.2 to patch the information disclosure vulnerability. If immediate patching is not possible, restrict API access to trusted networks and monitor for unauthorized data access.

Recommended fix High confidence

1.1.5 (or 1.0.2 for 1.0.x branch)

  1. Identify current Omni version by checking the installation or running 'omni --version'
  2. For 1.0.x branch: Upgrade to version 1.0.2
  3. For 1.1.x branch: Upgrade to version 1.1.5
  4. After upgrade, verify the API no longer exposes sensitive information by reviewing API responses
  5. Consult Omni release notes for any additional configuration changes required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Omni Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61688 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61688 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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