dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-33185

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
NVIDIA AIStore contains a vulnerability in AuthN where an unauthenticated user may cause information disclosure.  A successful exploit of this vulnerability may 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 confidence

NVIDIA AIStore contains an information disclosure vulnerability in its AuthN (authentication) component where an unauthenticated user can access sensitive information. The vulnerability stems from improper access controls in the authentication module, allowing attackers to bypass authentication checks and retrieve data they should not have access to.

MitigationImplement proper authentication enforcement and access controls in the AuthN module to ensure all sensitive operations require valid authentication. Apply vendor-provided patches when available and verify that unauthenticated endpoints do not expose sensitive data.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 NVIDIA AIStore installation
    Search for AIStore binaries, containers, or services. Common locations: /usr/local/ais, /opt/ais, or check running containers with 'docker ps | grep -i aistore' or 'kubectl get pods -A | grep -i aistore'
    Affected if AIStore is not installed - not affected. If present, continue to version check.
  2. Determine AIStore version
    Run 'ais version' if CLI is available, or check container image tags, or inspect binary with 'aisctl version', or look at deployment manifests/charts for version labels
    Affected if Version cannot be determined or is in the affected range - potential vulnerability exists. Compare to any vendor-advisory version bounds.
  3. Verify AuthN component is enabled
    Check AIStore configuration files (typically in /etc/ais or config directory) for authn.enabled or similar authentication flags. If using deployment manifests, look for authn or authentication service definitions.
    Affected if AuthN is explicitly disabled or not configured - may not be affected. If enabled or default, vulnerability applies.
  4. Inspect authentication endpoint exposure
    Review network listeners or API gateway configuration for unauthenticated endpoints. Check if port 8080/5100 (common AIStore ports) exposes /v1/auth or /authn paths without auth requirements. Use 'netstat -tlnp | grep ais' or review reverse proxy configs.
    Affected if Authentication endpoints are reachable without credentials or token validation is missing - vulnerable to unauthenticated access.
  5. Test for unauthenticated sensitive data access
    Send HTTP requests to typical sensitive endpoints (e.g., /v1/cluster, /v1/buckets, /v1/objects) without Authorization header using curl: 'curl -s http://<host>:<port>/v1/cluster'
    Affected if Requests return cluster metadata, bucket lists, or sensitive configuration without authentication - confirmed vulnerable.

If AIStore with an affected version has AuthN enabled and its authentication can be bypassed to access sensitive data without credentials, the environment is affected by CVE-2025-33185.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication enforcement and access controls in the AuthN module to ensure all sensitive operations require valid authentication. Apply vendor-provided patches when available and verify that unauthenticated endpoints do not expose sensitive data.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33185 — 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-33185 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