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

CVE-2026-45082

HIGH · 7.6 CVSS v3.1 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 →
82/100
Remediation priority · High
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
Karakeep is a elf-hostable bookmark-everything app. A Server-Side Request Forgery (SSRF) protection bypass vulnerability was identified in versions prior to 0.32.0 affecting redirect-following processing components. Although the application implements protections intended to prevent requests toward internal/private network destinations, these protections could be bypassed through crafted HTTP redirect chains. By leveraging attacker-controlled redirects, an authenticated user could cause vulnerable application components to initiate requests toward internally reachable Docker network services accessible from the application environment. The issue affected multiple processing paths, including crawler-related functionality and video download processing flows. Version 0.32.0 contains a patch.

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

Karakeep versions prior to 0.32.0 contain an SSRF protection bypass vulnerability in redirect-following processing components. Although the application implements protections against internal/private network requests, these can be bypassed through crafted HTTP redirect chains. Authenticated users can leverage attacker-controlled redirects to cause the application to make requests toward internally reachable Docker network services. The vulnerability affects crawler functionality and video download processing flows.

MitigationUpgrade to Karakeep version 0.32.0 or later which contains the patch for this SSRF bypass. If immediate upgrade is not possible, consider network segmentation to restrict the application's outbound connectivity and disable or rate-limit the affected crawler and video download features.

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

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 installed Karakeep version
    Run the version command for Karakeep (typically 'karakeep --version' or check the package manager if installed via apt/yum/docker)
    Affected if The version displayed is prior to 0.32.0 (e.g., 0.31.x, 0.30.x, etc.)
  2. Determine if crawler component is in use
    Inspect Karakeep configuration files or running services for crawler-related settings. Look for crawler-enabled flags or scheduled crawler jobs.
    Affected if Crawler functionality is enabled or configured in the environment
  3. Determine if video download processing is in use
    Inspect Karakeep configuration files or running services for video download-related settings. Look for video download module or processing queues.
    Affected if Video download processing is enabled or configured in the environment
  4. Check redirect-following configuration
    Examine Karakeep configuration for redirect-handling settings in crawler and video download components. Look for options controlling HTTP redirect behavior.
    Affected if Redirect-following is enabled (not disabled) for the affected components

You are affected if running Karakeep version prior to 0.32.0 AND either the crawler or video download component is enabled with redirect-following active.

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 Karakeep version 0.32.0 or later which contains the patch for this SSRF bypass. If immediate upgrade is not possible, consider network segmentation to restrict the application's outbound connectivity and disable or rate-limit the affected crawler and video download features.

Recommended fix High confidence

0.32.0

  1. Check current Karakeep installation version (e.g., via package manager, Docker tag, or application UI)
  2. Stop the running Karakeep service
  3. Backup the existing installation and any persistent data/storage
  4. Upgrade Karakeep to version 0.32.0 using the appropriate method for your deployment (e.g., Docker pull karakeep/karakeep:0.32.0, or package manager update)
  5. Restart the Karakeep service
  6. Verify the upgrade was successful by checking the running version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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