CVE-2025-23289
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 · uneditedNVIDIA Omniverse Launcher for Windows and Linux contains a vulnerability in the launcher logs, where a user could cause sensitive information to be written to the log files through proxy servers. A successful exploit of this vulnerability might lead to information disclosure.
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 confidenceNVIDIA Omniverse Launcher for Windows and Linux writes sensitive information to log files when proxy servers are used. The vulnerability allows a user to cause credentials, authentication tokens, or other sensitive proxy-related data to be written to launcher logs, leading to information disclosure.
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 NVIDIA Omniverse Launcher installationLocate the Omniverse Launcher installation directory and check the version information. On Windows, typical paths include AppData\Local\NVIDIA\Omniverse or Program Files\NVIDIA Corporation\Omniverse. On Linux, check ~/.local/share/NVIDIA/Omniverse or /opt/NVIDIA/Omniverse. Look for version info in launcher metadata or about dialog.Affected if The installed version has not been patched and proxy configuration is in use
-
Determine if proxy server is configuredCheck for proxy settings in the Omniverse Launcher configuration. Look for proxy environment variables (HTTP_PROXY, HTTPS_PROXY, ALL_PROXY), or proxy settings within the launcher UI under Network or Preferences settings.Affected if Proxy server configuration is active and the launcher is used to connect through it
-
Locate Omniverse Launcher log filesFind log files in the launcher directory or standard log locations. On Windows, check AppData\Local\NVIDIA\Omniverse\logs. On Linux, check ~/.local/share/NVIDIA/Omniverse/logs or ~/Omniverse/logs. Look for files with .log extension.Affected if Log files exist and were created while using proxy configuration
-
Inspect logs for sensitive proxy dataOpen the log files and search for patterns indicating credentials: look for strings containing 'password', 'token', 'auth', 'credential', 'proxy' combined with visible password-like values (anything after 'password=' or 'token=' that is not empty or masked). Also search for base64-encoded strings that may represent credentials.Affected if Log files contain visible proxy usernames, passwords, authentication tokens, or API keys in plain text
A user is affected if proxy server credentials or authentication tokens were configured in the Omniverse Launcher and log files exist in locations that could be accessed by other users or processes.
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 input sanitization or redaction for sensitive data in logging statements, particularly around proxy server configuration and authentication. Review all log paths to ensure no credentials or tokens are written to log files.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23289 — 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-23289 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