PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-64870 1Panel-dev CVE debrief

CVE-2026-64870 is a vulnerability in MaxKB, an open-source AI assistant for enterprise. In versions 2.0.0 through 2.10.4-lts, UpdateStoreTool.update_tool passes caller-supplied download_url and download_callback_url values to requests.get without equivalent trusted-host and redirect validation. This allows an authenticated workspace user to make the server request internal, loopback, link-local, or cloud metadata URLs.

Vendor
1Panel-dev
Product
MaxKB
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-30
Original CVE updated
2026-10-23
Advisory published
2026-07-30
Advisory updated
2026-10-23

Who should care

Defenders of systems using MaxKB versions 2.0.0 through 2.10.4-lts should assess exposure and prioritize applying the fix. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify the vulnerability's impact on their systems and apply the fix.

Why it matters

CVE-2026-64870 is a vulnerability in MaxKB that allows authenticated users to make server requests to internal, loopback, link-local, or cloud metadata URLs. Defenders of systems using MaxKB versions 2.0.0 through 2.10.4-lts should assess exposure and prioritize applying the fix.

  • Authenticated users may be able to make server requests to internal, loopback, link-local, or cloud metadata URLs
  • Defenders need to verify the vulnerability's impact on their systems and apply the fix

Technical summary

The vulnerability is caused by the UpdateStoreTool.update_tool function passing caller-supplied download_url and download_callback_url values to requests.get without equivalent trusted-host and redirect validation. This allows an authenticated workspace user to make the server request internal, loopback, link-local, or cloud metadata URLs. The vulnerability affects MaxKB versions 2.0.0 through 2.10.4-lts. Defenders should prioritize verifying the vulnerability's impact on their systems and applying the fix present on the v2 branch.

Defensive priority

Defenders should prioritize verifying the vulnerability's impact on their systems and applying the fix present on the v2 branch.

Recommended defensive actions

  • Verify the vulnerability's impact on your systems
  • Apply the fix present on the v2 branch
  • Monitor for potential exploitation attempts
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is described in the CVE record and NVD vulnerability detail page. A fix is present on the v2 branch but has not yet been included in a published release. The vulnerability allows an authenticated workspace user to make the server request internal, loopback, link-local, or cloud metadata URLs. Evidence is limited to the CVE record and NVD detail page. Defenders should verify the vulnerability's impact on their systems and apply the fix.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-64870 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-64870

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-64870 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64870

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.