CVE-2026-91924
pgweb through 0.17.0 leaves the POST /api/connect endpoint …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/sosedoff/pgweb
- github.com/sosedoff/pgweb/blob/6b0b0244d1aefd6971999b03481eeeaa4ec7cf55/pkg/api/api.go
- github.com/sosedoff/pgweb/blob/6b0b0244d1aefd6971999b03481eeeaa4ec7cf55/pkg/api/routes.go
- github.com/sosedoff/pgweb/issues/869
- www.vulncheck.com/advisories/pgweb-through-0.17.0-missing-authorization-on-direct-connect-
- nvd.nist.gov/vuln/detail/CVE-2026-91924
- cve.org/CVERecord?id=CVE-2026-91924
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.