CVE-2026-91924Disclosure

LOWCVSS 8.4 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-862

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-09-16: 1Technical Details · 2026-09-16: 109-16
Signal classification1 categories
Disclosure
1100.0%
Referenced assets1 URL
By indicator
Full discourse1 post
  • Upwind Security MDR@UpwindMDR
    Disclosure

    🚨HIGH - pgweb Unauthorized DB Connect via /api/connect Auth Bypass (CVE-2026-91924) pgweb exposes POST /api/connect without auth checks even when connect-backend authorization is configured. An attacker can set a custom session identifier and submit an arbitrary connection URL to bypass resource-to-database mapping, gaining unauthorized access to other DBs and internal services reachable from the pgweb host. 👉Affected: http://github.com/sosedoff/pgweb <= 0.17.0

    Post summary

    The text discloses a high-severity authentication bypass vulnerability in pgweb affecting versions up to 0.17.0, including specific endpoint and impact details. It does not indicate a PoC, exploit tool, active exploitation, or patch.

    0000066
    305 followersView on X

Explore more