What is the CVSS score of EUVD-2026-31826?

EUVD-2026-31826 has a CVSS 3.1 base score of 7.6 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L. EPSS exploitation probability: 0.0%.

Which versions of Karakeep are affected by EUVD-2026-31826?

Karakeep, a self-hosted bookmark management solution, contains a network security flaw in versions prior to 0.32.0 that allows authenticated users to circumvent network isolation controls and gain…. A patch is available.

How to fix or mitigate EUVD-2026-31826?

Within 24 hours: Identify all Karakeep deployments and confirm which instances run versions prior to 0.32.0; publicly available exploit code exists, so closure should be treated with urgency. Within 7 days: Upgrade all affected instances to Karakeep version 0.32.0. Within 30 days: Verify successful patching across all environments and perform a network segmentation audit to ensure internal services remain isolated.

Karakeep EUVD-2026-31826

| CVE-2026-45082 HIGH

Server-Side Request Forgery (SSRF) (CWE-918)

2026-05-26 GitHub_M

Docker SSRF Karakeep

7.6

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

7.6 HIGH

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

Primary rating from Vendor (GitHub_M) · only source for this CVE.

CVSS VectorVendor: GitHub_M

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

Low

Lifecycle Timeline

Analysis Generated

Jun 08, 2026 - 10:01 vuln.today

Patch available

May 26, 2026 - 16:02 EUVD

CVE Published

May 26, 2026 - 13:45 nvd

HIGH 7.6

DescriptionCVE.org

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.

AnalysisAI

Server-side request forgery in Karakeep self-hosted bookmark manager versions prior to 0.32.0 allows authenticated users to bypass internal-network protections by chaining attacker-controlled HTTP redirects, reaching Docker-internal services from the crawler and video download flows. Publicly available exploit code exists per SSVC, though EPSS is low at 0.03% and the issue is not in CISA KEV. Fixed in version 0.32.0.

Technical ContextAI

Karakeep (CPE karakeep-app:karakeep) is a Node.js-based self-hostable bookmark-everything application that fetches user-supplied URLs to scrape page metadata, archive content, and download embedded video. The vulnerability is a classic CWE-918 Server-Side Request Forgery: the application validates the initial URL against an internal/private-IP blocklist but follows HTTP 3xx redirects without re-validating each hop. Because Karakeep is typically deployed in Docker with sibling services (meilisearch, browser, postgres, chrome) on a shared user-defined bridge network, an attacker-controlled origin can return a redirect to a Docker DNS name or RFC1918 address and have the fetcher dereference it. The same redirect handling exists in multiple ingestion paths - the link crawler and the video downloader - multiplying the attack surface.

RemediationAI

Vendor-released patch: upgrade to Karakeep 0.32.0 or later, which adds redirect-aware SSRF validation; release notes and details are at https://github.com/karakeep-app/karakeep/security/advisories/GHSA-g647-327m-79g9. If immediate upgrade is not possible, restrict who can submit URLs by disabling open registration and auditing existing user accounts, and isolate the Karakeep containers from sensitive sibling services by placing them on a dedicated Docker network with egress restricted to the public internet via an egress proxy that re-validates each redirect hop against RFC1918/Docker-internal ranges - note this breaks legitimate fetching of any internal bookmarks and may slow scraping. As a narrower stopgap, disable the video download workers (KARAKEEP_CRAWLER_VIDEO_DOWNLOAD or equivalent) and accept that videos will not be archived. Do not rely on the application's built-in private-IP filter alone, since that is precisely what is bypassed.