dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-42337

MEDIUM · 5.3 CVSS v4.0 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
MaxKB is an open-source AI assistant for enterprise. MaxKB 2.8.0 and prior are vulnerable to a broken access control vulnerability in the OSS file service URL fetch API (chat/api/oss/get_url). The endpoint uses application_id from the URL path without validating ownership, allowing attackers to perform operations under other applications’ policies. This vulnerability is fixed in 2.8.1.

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

MaxKB 2.8.0 and prior contains a broken access control vulnerability in the OSS file service URL fetch API (chat/api/oss/get_url). The endpoint retrieves the application_id from the URL path without validating that the authenticated user owns or has access to that application, allowing unauthorized access to other applications' resources and policies.

MitigationUpgrade to MaxKB version 2.8.1 or later. Additionally, implement proper ownership validation for the application_id parameter in the affected endpoint to ensure users can only access resources within their authorized applications.

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:N/PR:L/UI:N/VC:L/VI:N/VA:N/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 MaxKB installation version
    Locate the MaxKB installation and check its version number (e.g., via Docker image tag, package.json, requirements.txt, version file, or admin UI about section). Compare against the affected range: versions 2.8.0 and prior.
    Affected if The installed version is 2.8.0 or lower.
  2. Verify vulnerable API endpoint exists
    Check if the endpoint /chat/api/oss/get_url is present in the MaxKB installation. This may involve reviewing the API routing configuration or searching for the endpoint path in the codebase.
    Affected if The endpoint exists in the codebase and the version is in the affected range.
  3. Inspect application_id validation logic
    Review the code handling the /chat/api/oss/get_url endpoint. Locate where application_id is extracted from the URL path and determine if there is an ownership or permission check validating that the requesting user has rights to that application_id.
    Affected if The code accepts application_id from the URL without validating user ownership or access permissions.
  4. Assess API accessibility
    Determine if the endpoint is exposed to users or external callers. Check authentication configuration and network access settings.
    Affected if The endpoint is accessible to authenticated users without proper authorization checks.

If MaxKB version is 2.8.0 or prior AND the /chat/api/oss/get_url endpoint processes application_id without ownership verification, the environment is affected by CVE-2026-42337.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to MaxKB version 2.8.1 or later. Additionally, implement proper ownership validation for the application_id parameter in the affected endpoint to ensure users can only access resources within their authorized applications.

Recommended fix High confidence

2.8.1

  1. Upgrade MaxKB from version 2.8.0 or prior to version 2.8.1
  2. After upgrading, verify that the chat/api/oss/get_url endpoint now properly validates application ownership before returning URLs

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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