DEV Community: CVE Reports

CVE-2026-88008: CVE-2026-88008: Middleware Security Bypass via Unencrypted HTTP/2 (h2c) Connection Upgrades in Traefik

CVE Reports — Fri, 11 Sep 2026 01:31:02 +0000

CVE-2026-88008: Middleware Security Bypass via Unencrypted HTTP/2 (h2c) Connection Upgrades in Traefik

Vulnerability ID: CVE-2026-88008
CVSS Score: 7.0
Published: 2026-09-10

An architectural flaw in the Traefik reverse proxy allows unauthenticated remote attackers to bypass security middlewares (such as basic authentication, IP allowlists, and forward authorization) by initiating an unencrypted HTTP/2 (h2c) upgrade request, causing the proxy to transition the connection into an opaque bi-directional TCP tunnel.

TL;DR

Unauthenticated remote attackers can bypass Traefik security middlewares by upgrading a connection to cleartext HTTP/2 (h2c) over an unrestricted route, establishing a raw TCP tunnel directly to the backend that allows uninspected multiplexed streams to reach private paths.

Technical Details

CWE ID: CWE-444 / CWE-863
Attack Vector: Network (N)
CVSS v4.0 Score: 7.0 (High)
EPSS Score: 0.00 (Pending)
Impact: Authentication & Middleware Policy Bypass
Exploit Status: Proof-of-Concept State
CISA KEV Status: Not Listed

Affected Systems

Traefik Proxy
Traefik: >= 2.11.26, < 2.11.57 (Fixed in: 2.11.57)
Traefik: >= 3.4.2, < 3.7.13 (Fixed in: 3.7.13)

Code Analysis

Commit: a277e94

Introduce h2cUpgradeHandler to strip client-initiated h2c upgrades and prevent reverse proxy tunneling bypass.

Mitigation Strategies

Upgrade Traefik to non-vulnerable release versions (v2.11.57 or v3.7.13)
Disable cleartext h2c upgrade support on all backend destination servers
Configure unencrypted backend endpoints using prior knowledge (h2c:// scheme) rather than transport upgrades

Remediation Steps:

Audit existing deployment files to check Traefik dynamic and static configuration structures.
Upgrade Traefik binary or Docker container image tag to 2.11.57 or 3.7.13.
Verify configuration files do not expose h2c backends using http:// schemas if h2c is enabled at the service layer.
Test endpoint compliance by sending a mock h2c upgrade request and ensuring the Upgrade header is excluded.

References

Read the full report for CVE-2026-88008 on our website for more details including interactive diagrams and full exploit analysis.

CVE-2026-88006: CVE-2026-88006: Incorrect Authorization in Open WebUI OAuth Token Exchange

CVE Reports — Fri, 11 Sep 2026 00:31:04 +0000

CVE-2026-88006: Incorrect Authorization in Open WebUI OAuth Token Exchange

Vulnerability ID: CVE-2026-88006
CVSS Score: 6.5
Published: 2026-09-10

An incorrect authorization vulnerability in Open WebUI allows users to bypass Identity Provider (IdP) role revocations and demotions. Prior to version 0.11.1, the OAuth token exchange endpoint failed to execute user synchronization and group mapping checks, enabling users with active provider tokens to establish sessions with their cached, stale database roles.

TL;DR

Open WebUI's token exchange endpoint bypassed Identity Provider role checks, letting demoted or revoked users access the application with stale, cached database privileges.

Technical Details

CWE ID: CWE-863 (Incorrect Authorization)
Attack Vector: Network
CVSS v3.1 Score: 6.5
Impact: Partial Privilege Escalation / Authorization Bypass
Exploit Status: None/Unproven
CISA KEV Status: Not Listed

Affected Systems

Open WebUI
Open WebUI: >= 0.8.0, < 0.11.1 (Fixed in: 0.11.1)

Code Analysis

Commit: d799e81

Refactor user synchronization and integrate role check inside token exchange endpoint

Mitigation Strategies

Upgrade Open WebUI to version 0.11.1 or higher.
Implement short-lived access tokens on the external Identity Provider.
Audit existing database roles periodically to align with the identity provider directory.

Remediation Steps:

Identify the running version of Open WebUI.
Download the v0.11.1 release or pull the updated Docker container image.
Deploy the updated application and restart the backend services.
Verify that requests to the /token/exchange endpoint trigger the role mapping checks.

References

Read the full report for CVE-2026-88006 on our website for more details including interactive diagrams and full exploit analysis.

CVE-2026-88016: CVE-2026-88016: Arbitrary Filesystem Metadata Modification and Directory Traversal in rclone

CVE Reports — Thu, 10 Sep 2026 23:30:31 +0000

CVE-2026-88016: Arbitrary Filesystem Metadata Modification and Directory Traversal in rclone

Vulnerability ID: CVE-2026-88016
CVSS Score: 7.1
Published: 2026-09-10

CVE-2026-88016 is a high-severity directory traversal and arbitrary metadata modification vulnerability in rclone versions prior to 1.75.1. When synchronizing directories with the --links and --metadata flags, rclone fails to apply sandboxing to directory metadata operations, leading to symbolic link following that allows modification of arbitrary files outside the target destination.

TL;DR

Directory-level metadata operations in rclone with the --links flag follow attacker-controlled symbolic links, allowing arbitrary filesystem metadata modifications and local privilege escalation.

⚠️ Exploit Status: POC

Technical Details

CWE ID: CWE-59
Attack Vector: Network
CVSS v3.1: 7.1
Impact: Local Privilege Escalation / Arbitrary Metadata Modification
Exploit Status: Proof-of-Concept
KEV Status: Not Listed

Affected Systems

rclone
rclone: < 1.75.1 (Fixed in: 1.75.1)

Code Analysis

Commit: a7ab39d

Local backend: Fix symlink traversal via directory metadata operations

Commit: 17b0c03

Local backend: Fix birth-time timestamp bypass when translating symlinks on Windows

Mitigation Strategies

Upgrade rclone to version 1.75.1 or later.
Disable the --links (-l) flag when syncing from untrusted sources.
Run the synchronization jobs with minimal system privileges.
Avoid using --metadata alongside --links in unpatched environments.

Remediation Steps:

Identify all systems and automated scripts running rclone.
Check the installed rclone version using rclone version.
Download and install rclone version 1.75.1 or higher.
As an interim control, review the use of the --links and --metadata arguments.

References

Read the full report for CVE-2026-88016 on our website for more details including interactive diagrams and full exploit analysis.

GHSA-M3WP-48JR-VR4G: GHSA-m3wp-48jr-vr4g: Unbounded Remote Media Fetch and Video Frame Expansion DoS in mistral.rs

CVE Reports — Thu, 10 Sep 2026 22:30:31 +0000

GHSA-m3wp-48jr-vr4g: Unbounded Remote Media Fetch and Video Frame Expansion DoS in mistral.rs

Vulnerability ID: GHSA-M3WP-48JR-VR4G
CVSS Score: 7.5
Published: 2026-09-10

An unbounded resource consumption and server-side request forgery (SSRF) vulnerability in mistral.rs allows remote, unauthenticated attackers to cause a denial of service (DoS) or execute SSRF attacks. The flaw exists in mistralrs-server-core due to unchecked remote media fetching, infinite stream buffering, and unbounded FFmpeg frame extraction.

TL;DR

Unauthenticated remote attackers can crash the mistral.rs server via Out-Of-Memory (OOM) or exhaust storage/CPU resources by sending crafted media URLs to the completions API.

⚠️ Exploit Status: POC

Technical Details

CWE ID: CWE-400, CWE-918
Attack Vector: Network (AV:N)
CVSS Severity: 7.5 (High)
Exploit Status: Proof-of-Concept Publicly Available
KEV Status: Not Listed
Impact: Denial of Service (OOM/Disk Exhaustion), SSRF

Affected Systems

mistral.rs
mistralrs-server-core
mistralrs-server-core: < 0.8.18 (Fixed in: v0.8.18)

Mitigation Strategies

Upgrade mistral.rs to v0.8.18 or later.
Apply egress firewall filters to drop connections to internal and loopback IP spaces.
Implement Nginx reverse-proxy request payload limits and timeouts.
Remove system ffmpeg binaries if video parsing is not required in production.

Remediation Steps:

Check current mistral.rs server version utilizing 'cargo tree' or dependency manifest audits.
Modify Cargo.toml dependency targets for mistralrs-server-core to version >= 0.8.18.
Rebuild application using updated crates.io packages and verify media_source.rs features are active.
Add egress rules in iptables to restrict host server from querying local network assets.

References

Read the full report for GHSA-M3WP-48JR-VR4G on our website for more details including interactive diagrams and full exploit analysis.

CVE-2026-86083: CVE-2026-86083: Sandbox Escape and Remote Code Execution via Code-Printer Injection in n8n Legacy Expression Engine

CVE Reports — Thu, 10 Sep 2026 21:30:29 +0000

CVE-2026-86083: Sandbox Escape and Remote Code Execution via Code-Printer Injection in n8n Legacy Expression Engine

Vulnerability ID: CVE-2026-86083
CVSS Score: 7.7
Published: 2026-09-10

A critical sandbox escape vulnerability exists in the legacy expression engine of n8n. By leveraging Shared Builtin Tampering combined with Code-Printer Injection, an authenticated attacker can hijack the mutable global JSON.stringify function. This hijacking allows the attacker to inject arbitrary Node.js source code into internal execution contexts during code generation, escaping the isolated-vm sandbox and achieving full remote code execution on the host system.

TL;DR

An authenticated user can bypass the isolated-vm sandbox in n8n's legacy expression engine by poisoning the global JSON.stringify function, leading to arbitrary host command execution.

⚠️ Exploit Status: POC

Technical Details

CWE ID: CWE-94
Attack Vector: Network
CVSS v4.0 Score: 7.7
Exploit Status: PoC Available
KEV Status: Not Listed

Affected Systems

n8n open-source workflow automation platform using legacy expression engine
n8n: < 1.123.76 (Fixed in: 1.123.76)
n8n: >= 2.0.0, < 2.37.7 (Fixed in: 2.37.7)
n8n: >= 2.38.0, < 2.38.2 (Fixed in: 2.38.2)

Mitigation Strategies

Upgrade n8n to version 1.123.76, 2.37.7, 2.38.2 or later
Configure N8N_EXPRESSION_ENGINE environment variable to 'vm'
Employ non-root container isolation for the n8n process

Remediation Steps:

Identify the current n8n version in deployment
Deploy the appropriate patch release from n8n's official distribution channel
Alternatively, export the environment variable N8N_EXPRESSION_ENGINE=vm in the deployment configuration
Restart the n8n container or service daemon to apply the configuration
Verify that legacy expression engine warnings are no longer logged

References

Read the full report for CVE-2026-86083 on our website for more details including interactive diagrams and full exploit analysis.

CVE-2026-87017: CVE-2026-87017: Broken Object-Level Authorization (BOLA) in Open WebUI Knowledge Search

CVE Reports — Thu, 10 Sep 2026 20:30:31 +0000

CVE-2026-87017: Broken Object-Level Authorization (BOLA) in Open WebUI Knowledge Search

Vulnerability ID: CVE-2026-87017
CVSS Score: 4.3
Published: 2026-09-10

A Broken Object-Level Authorization (BOLA) vulnerability exists in Open WebUI starting from version 0.7.0 up to (but not including) 0.11.1. The flaw resides in the platform's built-in knowledge search tool, which constructs metadata filters to scope database queries based on user permissions. However, eleven of the fifteen shipped vector database backends accepted these filters but silently ignored them, enabling authenticated users to retrieve and enumerate the metadata of inaccessible or private knowledge bases.

TL;DR

Eleven of fifteen vector database backends in Open WebUI ignored query filters, allowing authenticated users to enumerate metadata of unauthorized knowledge bases.

⚠️ Exploit Status: POC

Technical Details

CWE ID: CWE-863
Attack Vector: Network (AV:N)
CVSS v3.1 Score: 4.3 (Medium)
Exploit Status: Proof-of-Concept (PoC) / Known Root Cause
KEV Status: Not Listed
Affected Components: Vector database client adapters

Affected Systems

Open WebUI
Open WebUI: >= 0.7.0, < 0.11.1 (Fixed in: 0.11.1)

Code Analysis

Commit: 1d6d4e6

Explicitly translate, parse, and apply metadata filters across affected vector database backends.

Mitigation Strategies

Upgrade to Open WebUI version 0.11.1 or later.
Disable the built-in knowledge search tool for low-privilege roles.
Switch the active vector store backend to Chroma.
Isolate sensitive knowledge bases in dedicated vector database instances.

Remediation Steps:

Identify the current running version of Open WebUI.
If running any version from 0.7.0 through 0.11.0, prepare the environment for an upgrade.
Pull the latest Docker image or update the Git repository to version 0.11.1.
Restart the Open WebUI container or service.
Verify the configuration of the active vector database backend.

References

Read the full report for CVE-2026-87017 on our website for more details including interactive diagrams and full exploit analysis.

CVE-2026-86076: CVE-2026-86076: Remote Code Execution via Expression Sandbox Escape in n8n

CVE Reports — Thu, 10 Sep 2026 19:30:31 +0000

CVE-2026-86076: Remote Code Execution via Expression Sandbox Escape in n8n

Vulnerability ID: CVE-2026-86076
CVSS Score: 8.7
Published: 2026-09-10

An expression sandbox escape vulnerability exists in n8n due to a missing AST traversal check on ClassBody in the PrototypeSanitizer. This allows authenticated users with low privileges to bypass property checks and achieve remote code execution.

TL;DR

A missing ClassBody traversal in n8n's expression sanitizer allows low-privileged users to redefine the '__sanitize' resolver on custom classes, escaping the sandbox to execute arbitrary Node.js commands.

Technical Details

CWE ID: CWE-94
Attack Vector: Network
CVSS Score: 8.7 (High)
Impact: Remote Code Execution (RCE) / Stored Cross-User JavaScript Execution
Exploit Status: PoC (Proof of Concept) Feasible
KEV Status: Not Listed

Affected Systems

n8n Workflow Automation Platform
n8n: < 1.123.76 (Fixed in: 1.123.76)
n8n: >= 2.0.0, < 2.37.7 (Fixed in: 2.37.7)
n8n: >= 2.38.0, < 2.38.2 (Fixed in: 2.38.2)

Mitigation Strategies

Upgrade n8n immediately to version 1.123.76, 2.37.7, or 2.38.2 to resolve the missing AST check.
Audit stored workflow configurations within the system database to identify unauthorized expressions.
Enforce strict Role-Based Access Control (RBAC) to ensure untrusted users cannot author workflows.

Remediation Steps:

Locate the active deployment and execute the version bump (e.g., 'docker pull n8n-io/n8n:2.38.2').
Scan the workflow database using SQL queries for occurrence of '__sanitize' within the workflow definitions.
Restrict workspace configuration and editing privileges to administrative roles.

References

Read the full report for CVE-2026-86076 on our website for more details including interactive diagrams and full exploit analysis.

CVE-2026-86075: CVE-2026-86075: Unauthenticated Persistent Storage Exhaustion via OAuth Dynamic Client Registration Endpoint in n8n

CVE Reports — Thu, 10 Sep 2026 18:30:29 +0000

CVE-2026-86075: Unauthenticated Persistent Storage Exhaustion via OAuth Dynamic Client Registration Endpoint in n8n

Vulnerability ID: CVE-2026-86075
CVSS Score: 8.7
Published: 2026-09-10

In vulnerable configurations of n8n, the OAuth Dynamic Client Registration endpoint implements field size validation for redirect_uris but fails to enforce proper limits on client_name and grant_types. This allows an unauthenticated remote attacker to submit arbitrarily large values for these fields, leading to persistent database and disk storage exhaustion.

TL;DR

An unauthenticated remote attacker can cause a complete Denial of Service (DoS) of the n8n platform by submitting excessively large registration payloads containing bloated client_name and grant_types fields, which exhausts backend persistent storage.

Technical Details

CWE ID: CWE-770
Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
CVSS v4.0: 8.7 (High)
Exploit Status: None
KEV Status: Not Listed

Affected Systems

n8n Workflow Automation Platform
n8n: < 2.37.7 (Fixed in: 2.37.7)
n8n: >= 2.38.0, < 2.38.2 (Fixed in: 2.38.2)

Mitigation Strategies

Upgrade n8n to version 2.37.7, 2.38.2, or later
Configure WAF payload limits on registration endpoints
Implement rate limiting per source IP for OAuth registration routes

Remediation Steps:

Identify the deployed n8n version and branch.
If running < 2.37.7, upgrade to 2.37.7.
If running 2.38.0 or 2.38.1, upgrade to 2.38.2.
Monitor database table metrics for the oauth_clients table to detect bloat.

References

Read the full report for CVE-2026-86075 on our website for more details including interactive diagrams and full exploit analysis.

CVE-2025-21587: CVE-2025-21587: Timing Side-Channel Vulnerability in JSSE RSA Decryption

CVE Reports — Thu, 10 Sep 2026 17:31:32 +0000

CVE-2025-21587: Timing Side-Channel Vulnerability in JSSE RSA Decryption

Vulnerability ID: CVE-2025-21587
CVSS Score: 7.4
Published: 2025-04-15

CVE-2025-21587 is a high-severity timing side-channel vulnerability in the Java Secure Socket Extension (JSSE) component of Oracle Java SE and GraalVM. The flaw allows unauthenticated network attackers to perform Bleichenbacher-style (Marvin) decryption oracle attacks, potentially compromising TLS session confidentiality.

TL;DR

A timing side-channel in JSSE allows remote attackers to decrypt TLS traffic or forge signatures by exploiting non-constant-time RSA unpadding operations.

⚠️ Exploit Status: POC

Technical Details

CWE ID: CWE-385
Attack Vector: Network (High Complexity)
CVSS Score: 7.4 (High)
EPSS Score: 0.00784 (53.94%)
Impact: Confidentiality and Integrity Compromise
Exploit Status: Proof of Concept (Theoretical)
KEV Status: Not Listed

Affected Systems

Oracle Java SE
Oracle GraalVM for JDK
Oracle GraalVM Enterprise Edition
Debian OpenJDK
Ubuntu OpenJDK
Oracle Java SE: 8u441, 11.0.26, 17.0.14, 21.0.6, 24 (Fixed in: 8u451, 11.0.27, 17.0.15, 21.0.7, 24.0.1)
Oracle GraalVM for JDK: 17.0.14, 21.0.6, 24 (Fixed in: 17.0.15, 21.0.7, 24.0.1)
Oracle GraalVM Enterprise Edition: 20.3.17, 21.3.13 (Fixed in: CPU April 2025 Patches)

Code Analysis

Commit: 73aa304

Upstream fix in OpenJDK 17u implementing unpadForTls helper to establish constant-time processing

Commit: d5c94ad

Upstream constant-time fix in OpenJDK 21u

Commit: 2adb01e

Upstream constant-time fix in OpenJDK 11u

Commit: 3cdd308

Upstream constant-time fix in OpenJDK 8u

Mitigation Strategies

Disable static RSA key exchange suites (TLS_RSA_*) and enforce Forward Secrecy (ECDHE/DHE).
Deploy Java security updates containing the April 2025 Critical Patch Update.
Enforce TLS 1.3 across exposed network interfaces to naturally eliminate RSA key exchange vectors.

Remediation Steps:

Identify all active JRE and JDK installations hosting TLS services.
Apply the corresponding patched version (e.g., 8u451, 11.0.27, 17.0.15, 21.0.7, 24.0.1 or higher).
Modify local server configuration files (such as Tomcat server.xml or Spring Boot properties) to remove cipher suites starting with TLS_RSA.
Monitor network traffic for an anomalous spike in TLS alerts (specifically Alert 20 or 51).

References

Read the full report for CVE-2025-21587 on our website for more details including interactive diagrams and full exploit analysis.

CVE-2026-86081: CVE-2026-86081: Regular Expression Denial of Service in n8n Git Node

CVE Reports — Thu, 10 Sep 2026 17:31:02 +0000

CVE-2026-86081: Regular Expression Denial of Service in n8n Git Node

Vulnerability ID: CVE-2026-86081
CVSS Score: 7.1
Published: 2026-09-10

A Regular Expression Denial of Service (ReDoS) vulnerability exists in n8n due to inefficient validation in its default blocked-file-pattern matching mechanism. This flaw can be triggered during Git operations, allowing authenticated workflow editors to cause resource exhaustion and completely freeze the n8n application process.

TL;DR

An authenticated user with workflow editing privileges can trigger exponential backtracking in n8n's file validation regular expression, blocking the single-threaded Node.js event loop and rendering the entire instance unavailable.

⚠️ Exploit Status: POC

Technical Details

CWE ID: CWE-1333
Attack Vector: Network
CVSS v4.0 Score: 7.1
EPSS Score: 0.00322
Exploit Status: poc
CISA KEV Status: Not Listed

Affected Systems

n8n Workflow Automation Platform
n8n: < 1.123.76 (Fixed in: 1.123.76)
n8n: >= 2.0.0 < 2.37.7 (Fixed in: 2.37.7)
n8n: >= 2.38.0 < 2.38.2 (Fixed in: 2.38.2)

Mitigation Strategies

Upgrade n8n deployment to a patched release containing the hardened regular expression.
Define the environment variable N8N_BLOCK_FILE_PATTERNS using the secure regex to override the vulnerable default configuration.

Remediation Steps:

For Docker-based deployments, update the container image tag to 1.123.76, 2.37.7, or 2.38.2.
If immediate patching is unavailable, append N8N_BLOCK_FILE_PATTERNS='^(?:[^/]*/)*\.git(?:/.*)?$' to the server environment variables.
Restart the n8n service to apply the updated environment configuration.

References

Read the full report for CVE-2026-86081 on our website for more details including interactive diagrams and full exploit analysis.

CVE-2026-86082: CVE-2026-86082: Server-Side Request Forgery and Credential Leakage in n8n OpenAI Chat Model Node

CVE Reports — Thu, 10 Sep 2026 16:30:30 +0000

CVE-2026-86082: Server-Side Request Forgery and Credential Leakage in n8n OpenAI Chat Model Node

Vulnerability ID: CVE-2026-86082
CVSS Score: 7.1
Published: 2026-09-10

CVE-2026-86082 is a critical Server-Side Request Forgery (SSRF) and credential leakage vulnerability in n8n. The flaw exists in the OpenAI Chat Model node's searchModels function, which fails to enforce credential domain restrictions when populating the model dropdown list. This allows an authenticated workflow editor to exfiltrate plaintext OpenAI API keys to an arbitrary attacker-controlled domain by specifying a custom baseURL override.

TL;DR

An authenticated workflow editor can bypass credential domain restrictions in n8n's OpenAI Chat Model node, causing the backend to send plaintext OpenAI API keys to an arbitrary server during dynamic model search.

⚠️ Exploit Status: POC

Technical Details

CWE ID: CWE-918
Attack Vector: Network
CVSS Score: 7.1 (High)
Exploit Status: Proof of Concept (PoC) documented
CISA KEV Status: Not Listed
EPSS Score: 0.00246 (Percentile: 15.84%)
Impact: Plaintext Credential Leakage / Server-Side Request Forgery (SSRF)

Affected Systems

n8n
n8n-nodes-langchain
n8n: < 1.123.76 (Fixed in: 1.123.76)
n8n: >= 2.0.0, < 2.37.7 (Fixed in: 2.37.7)
n8n: >= 2.38.0, < 2.38.2 (Fixed in: 2.38.2)

Code Analysis

Commit: cbee391

Fix: Enforce domain restrictions in OpenAI model loader

Commit: 2a4ca78

Fix: Apply security assertions in OpenAI LMChat model search (2.37.7 backport)

Commit: 7bd63f4

Fix: Restrict custom baseURL for OpenAI model population in 2.38.2 release

Exploit Details

GitHub Security Advisory: Advisory documenting vulnerability mechanics, reproduction steps, and exploit details.

Mitigation Strategies

Upgrade n8n immediately to one of the patched releases: 1.123.76, 2.37.7, or 2.38.2.
Monitor egress connections from the n8n application containers to block unauthorized API endpoints.
Limit authorization for Workflow Editor roles to trusted organizational personnel.
Rotate all potentially exposed OpenAI API keys immediately.

Remediation Steps:

Identify all running instances of n8n and verify their current version numbers.
Apply the patch by deploying docker image tags n8n@1.123.76, n8n@2.37.7, or n8n@2.38.2.
Review n8n workspace settings and verify credentials configuration audit logs.
In the OpenAI developer dashboard, revoke and replace all keys mapped to active n8n instances.
Establish custom egress firewall policies restricting the n8n environment's outbound communication to verified domains.

References

Read the full report for CVE-2026-86082 on our website for more details including interactive diagrams and full exploit analysis.

GHSA-HXJG-93WC-H8P8: GHSA-hxjg-93wc-h8p8: Cross-Site Request Forgery in Komari Management Interface

CVE Reports — Thu, 10 Sep 2026 05:30:31 +0000

GHSA-hxjg-93wc-h8p8: Cross-Site Request Forgery in Komari Management Interface

Vulnerability ID: GHSA-HXJG-93WC-H8P8
CVSS Score: 8.8
Published: 2026-09-09

A high-severity Cross-Site Request Forgery (CSRF) vulnerability exists in the Komari server monitoring tool. The administrative interface sets authentication cookies without restrictive SameSite or Secure attributes, and lacks any CSRF validation, enabling unauthenticated remote attackers to execute arbitrary commands or modify backend settings by exploiting administrative sessions.

TL;DR

Unauthenticated remote attackers can execute arbitrary shell commands on managed nodes and disable administrative 2FA by tricking an authenticated administrator into visiting a malicious link.

⚠️ Exploit Status: POC

Technical Details

CWE ID: CWE-352 (Cross-Site Request Forgery)
Attack Vector: Network (AV:N)
CVSS Severity: 8.8 (High)
Exploit Maturity: Proof of Concept (PoC)
Impact: Remote Code Execution / Privilege Escalation
First Patched Version: 1.2.2

Affected Systems

Komari Monitoring Server (github.com/komari-monitor/komari)
github.com/komari-monitor/komari: < 0.0.0-20260609084633-98122fa4d110 (Fixed in: 1.2.2)

Mitigation Strategies

Explicitly configure the session cookie with 'Secure=true' and 'SameSite=Lax' properties.
Implement CSRF validation middleware on all state-changing endpoints (/api/admin/*).
Utilize Double-Submit Cookie patterns or custom HTTP header validation.

Remediation Steps:

Upgrade the Komari server application to version 1.2.2 or higher.
If immediate upgrade is not viable, enforce reverse-proxy level validation of the HTTP 'Origin' and 'Referer' headers.
Enable HTTPS strictly to prevent session cookie leakage over unencrypted channels.

References

Read the full report for GHSA-HXJG-93WC-H8P8 on our website for more details including interactive diagrams and full exploit analysis.