dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-41090

HIGH · 7.6 CVSS v4.0 Published 2025-10-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable 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
microCLAUDIA in v3.2.0 and prior has an improper access control vulnerability. This flaw allows an authenticated user to perform unauthorized actions on other organizations' systems by sending direct API requests. To do so, the attacker can use organization identifiers obtained through a compromised endpoint or deduced manually. This vulnerability allows access between tenants, enabling an attacker to list and manage remote assets, uninstall agents, and even delete vaccines configurations.

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 confidence

microCLAUDIA versions 3.2.0 and prior contain an improper access control vulnerability allowing authenticated users in one tenant to access, list, modify, or delete resources belonging to other organizations by manipulating organization identifiers in direct API requests. This multi-tenancy authorization bypass enables attackers to manage remote assets, uninstall agents, and delete vaccine configurations across tenant boundaries.

MitigationImplement proper tenant isolation and authorization validation on all API endpoints that accept organization identifiers, ensuring the authenticated user's session context matches the requested organization before performing any action.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 the installed microCLAUDIA version
    Run the command to retrieve the microCLAUDIA version (commonly: 'microclaudia --version', check the product UI about page, or inspect the installed package metadata file)
    Affected if The installed version is 3.2.0 or any version prior to 3.2.0
  2. Confirm multi-tenancy is enabled
    Check the microCLAUDIA configuration file or admin console for tenant/organization management settings - look for multi-tenant mode, organization support, or tenant isolation configuration flags
    Affected if Multi-tenancy with multiple organizations is configured and active
  3. Verify API endpoint organization parameter handling
    Review API documentation or intercept API calls to identify endpoints that accept organization_id, org_id, tenant_id, or organization identifiers as request parameters
    Affected if The API accepts organization identifiers in request parameters without validating they belong to the authenticated user's session
  4. Inspect authorization configuration for tenant context validation
    Examine the authorization or access control configuration files to determine if API requests validate that the authenticated user's organization matches the requested organization identifier
    Affected if No explicit tenant context validation exists between the user's session organization and the organization identifier in API requests

A user is affected if they run microCLAUDIA version 3.2.0 or prior with multi-tenancy enabled, where the API accepts organization identifiers without validating the authenticated user's session matches the requested organization.

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 tenant isolation and authorization validation on all API endpoints that accept organization identifiers, ensuring the authenticated user's session context matches the requested organization before performing any action.

Have this fixed Scoped from the published advisory
  • Consultation12.0 h
  • Implementation32.0 h
  • Testing20.0 h
  • Review / QA8.0 h
72.0 hours of engineering $12,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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