CVE-2026-42336
Server-Side Request Forgery Bypass in MaxKB
Publication date: 2026-05-26
Last updated on: 2026-05-26
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| maxkb | maxkb | to 2.8.1 (exc) |
| maxkb | maxkb | 2.8.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
| CWE-367 | The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in MaxKB versions 2.8.0 and prior is a server-side request forgery (SSRF) bypass. It occurs in the OSS file service URL fetch functionality due to inconsistent DNS resolution between the validation step and the actual request execution. This inconsistency allows attackers to bypass security checks and access internal network services that should be protected.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to access internal network services that are normally not accessible from outside the network. This could lead to unauthorized access to sensitive internal resources, potential data exposure, or further exploitation within the internal network.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade MaxKB to version 2.8.1 or later, where the SSRF bypass issue has been fixed.