Vulnerability from bitnami_vulndb
Published
2026-05-12 08:52
Modified
2026-05-12 09:14
Summary
PgBouncer buffer overflow in SCRAM
Details

The SCRAM code in PgBouncer before 1.25.2 did not check the return value of strlcat() correctly when building the contents of the SCRAM client-final-message. A malicious backend that sends a SCRAM server-final-message with a long nonce can trigger a stack overflow.


{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "pgbouncer",
        "purl": "pkg:bitnami/pgbouncer"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.25.2"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "type": "CVSS_V3"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-6665"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:pgbouncer:pgbouncer:*:*:*:*:*:*:*:*"
    ],
    "severity": "High"
  },
  "details": "The SCRAM code in PgBouncer before 1.25.2 did not check the return value of strlcat() correctly when building the contents of the SCRAM client-final-message. A malicious backend that sends a SCRAM server-final-message with a long nonce can trigger a stack overflow.",
  "id": "BIT-pgbouncer-2026-6665",
  "modified": "2026-05-12T09:14:35.689Z",
  "published": "2026-05-12T08:52:51.850Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-6665"
    },
    {
      "type": "WEB",
      "url": "https://www.pgbouncer.org/changelog.html#pgbouncer-125x"
    }
  ],
  "schema_version": "1.6.2",
  "summary": "PgBouncer buffer overflow in SCRAM"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…