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

CVE-2026-45412

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.9.1, SSRF via work_flow_template Import. Authenticated users can supply arbitrary URLs in work_flow_template.downloadUrl which are fetched server-side without any URL validation or internal IP filtering. This vulnerability is fixed in 2.9.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

In MaxKB versions prior to 2.9.1, the work_flow_template import feature accepts a user-supplied downloadUrl parameter without performing URL validation or internal IP filtering. When an authenticated user provides an arbitrary URL, the server fetches that URL server-side, enabling Server-Side Request Forgery (SSRF) attacks that could target internal services, metadata endpoints, or other internal infrastructure.

MitigationUpgrade to MaxKB version 2.9.1 or later. If immediate patching is not possible, implement URL allowlist validation and block requests to internal/private IP ranges (including 127.0.0.1, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) at the application layer.

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:H/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 version
    Locate the installed MaxKB version file or check the application version endpoint (commonly /api/version or via CLI: maxkb --version). Compare the version number to 2.9.1.
    Affected if The installed version is below 2.9.1 (e.g., 2.9.0, 2.8.x, etc.)
  2. Verify work_flow_template import feature exists
    Check if the workflow import functionality is present in the MaxKB installation. Look for API endpoints related to work_flow_template, typically under /api/work-flow-template or /api/workflow/import in the application routing configuration.
    Affected if The work_flow_template import feature is present and exposed via API
  3. Confirm authentication is required
    Inspect the authentication configuration for the workflow import endpoint. Check if the endpoint requires valid user credentials (session token, API key, or login) to access.
    Affected if The endpoint accepts requests from any authenticated user (not limited to admin/specific roles)
  4. Check for URL validation on downloadUrl parameter
    Review application code or configuration for URL validation logic applied to the downloadUrl parameter in the work_flow_template import function. Look for allowlist logic, hostname/IP validation, or restriction checks.
    Affected if No URL validation or internal IP filtering is implemented for the downloadUrl parameter

You are affected if MaxKB version is below 2.9.1 AND the work_flow_template import feature is accessible to authenticated users without URL validation on the downloadUrl parameter.

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.9.1 or later. If immediate patching is not possible, implement URL allowlist validation and block requests to internal/private IP ranges (including 127.0.0.1, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) at the application layer.

Recommended fix High confidence

MaxKB version 2.9.1

  1. 1. Back up your current MaxKB installation and database before upgrading.
  2. 2. Check your current MaxKB version to confirm it is below 2.9.1.
  3. 3. Upgrade MaxKB to version 2.9.1. For Docker installations, update your image tag or docker-compose file to use the 2.9.1 release. For source installations, pull the v2.9.1 tag from the GitHub repository and reinstall.
  4. 4. Verify the upgrade was successful by checking the installed version.
  5. 5. Test that the work_flow_template import functionality now properly validates URLs and blocks internal IP addresses.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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