CVE-2026-91924
Received Received - Intake

pgweb Unauthorized Database Access via Arbitrary Connection String

Publication date: 2026-09-15

Last updated on: 2026-09-15

Assigner: VulnCheck

Description
pgweb through 0.17.0 leaves the POST /api/connect endpoint unguarded when connect-backend authorization is configured, allowing attackers to supply arbitrary database connection strings. Attackers can bypass the resource-to-database mapping by providing a custom session identifier and connection URL to access unauthorized databases and internal services.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-15
Last Modified
2026-09-15
Generated
2026-09-15
AI Q&A
2026-09-15
EPSS Evaluated
N/A
NVD
CVE-2026-91924
EUVD
EUVD-2026-78415

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
pgweb pgweb to 0.17.0 (inc)
sosedoff pgweb to 0.17.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects pgweb versions up to 0.17.0. When the Connect feature is enabled with specific flags, the POST /api/connect endpoint lacks proper authorization checks. Attackers can bypass backend authorization by supplying arbitrary database connection strings, allowing access to unauthorized databases and internal services.

Detection Guidance

Check if pgweb is running with the Connect feature enabled by inspecting running processes for flags like --sessions, --connect-backend, or --connect-token. Verify if the /api/connect endpoint is accessible without proper authorization checks.

Impact Analysis

An attacker could gain unauthorized access to sensitive databases, bypassing intended restrictions. This may lead to data breaches, exposure of confidential information, or internal network probing through error responses. The impact depends on the databases accessible from the pgweb host.

Compliance Impact

This vulnerability could lead to unauthorized data access, violating compliance requirements for data protection such as GDPR (data confidentiality) and HIPAA (protected health information). Organizations using affected pgweb versions may face regulatory penalties and reputational damage.

Mitigation Strategies

Upgrade pgweb to a version that patches this vulnerability. If upgrading is not possible, disable the Connect feature by removing --sessions, --connect-backend, and --connect-token flags. Restrict network access to pgweb instances to trusted users only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-91924. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart