dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-42335

MEDIUM · 6.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 →
69/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. Prior to 2.8.1, MaxKB v2.8.0 and prior are vulnerable to a server-side request forgery (SSRF) bypass in the OSS file service URL fetch (chat/api/oss/get_url) endpoint. The vulnerability exists due to inconsistent URL parsing between the urlparse validation function and the requests HTTP client, allowing attackers to access internal network services. 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 · moderate confidence

MaxKB versions 2.8.0 and prior contain an SSRF bypass vulnerability in the chat/api/oss/get_url endpoint. The vulnerability stems from inconsistent URL parsing between Python's urlparse validation function and the requests HTTP library, allowing attackers to bypass validation checks and access internal network services by crafting URLs that pass validation but are interpreted differently by the HTTP client.

MitigationUpgrade MaxKB to version 2.8.1 or later. For organizations unable to upgrade immediately, implement network segmentation and restrict outbound access from the application server to prevent internal service access.

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:N/VI:N/VA:N/SC:H/SI:L/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 and version
    Locate the MaxKB application installation and determine the installed version number. Compare it against the affected range: versions 2.8.0 and prior.
    Affected if The installed version is 2.8.0 or any prior version (e.g., 2.7.x, 2.6.x, etc.).
  2. Confirm the vulnerable endpoint exists
    Inspect the application codebase or API routing configuration for the presence of the /chat/api/oss/get_url endpoint.
    Affected if The endpoint is present in the application routing.
  3. Check if OSS file service feature is configured
    Examine the MaxKB configuration files or settings for any OSS (Object Storage Service) related configuration that enables the get_url functionality.
    Affected if OSS file service feature is enabled or configured in the environment.
  4. Verify internal network access from application
    Determine if the application has the ability to make outbound HTTP requests to internal network addresses.
    Affected if The application can initiate HTTP requests to internal services from the server.

A user is affected if MaxKB version is 2.8.0 or prior AND the OSS file service feature via the chat/api/oss/get_url endpoint is enabled.

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 MaxKB to version 2.8.1 or later. For organizations unable to upgrade immediately, implement network segmentation and restrict outbound access from the application server to prevent internal service access.

Recommended fix High confidence

MaxKB version 2.8.1

  1. Upgrade MaxKB from any version prior to 2.8.1 (including 2.8.0 and earlier) to version 2.8.1 or later to remediate the SSRF vulnerability in the chat/api/oss/get_url endpoint.
  2. After upgrading, verify the OSS file service URL fetch functionality (chat/api/oss/get_url) works correctly with the patched URL parsing logic.
  3. Review any internal network access controls as a defense-in-depth measure, though the patch addresses the root cause.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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