AWS Advanced Go Wrapper privilege escalation in Aurora PostgreSQL dialect detection

Check whether my systems are affected by CVE-2026-126793 (Privilege escalation in Aurora PostgreSQL dialect detection in AWS Advanced Go Wrapper), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126793 (entry last updated 2026-11-12):
Affected:
- AWS aws-advanced-go-wrapper: from 2026-04-06, fixed in 2026-07-29
Fixed versions: 2026-07-29.
Conditions (all must be true for the bug to be hit):
- Uses AWS Advanced Go Wrapper awssql/v2 from 2.0.0 before 2.0.3 (release 2026-04-06 up to before 2026-07-29) (source: https://aws.amazon.com/security/security-bulletins/2026-182-aws/)
- Victim connects to an Aurora PostgreSQL cluster through the affected wrapper version (source: https://aws.amazon.com/security/security-bulletins/2026-182-aws/)
- Attacker can create functions in a schema on the victim's search path (source: https://aws.amazon.com/security/security-bulletins/2026-182-aws/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
Workaround: Revoke CREATE on the public schema from PUBLIC, and grant CREATE on other search_path schemas only to trusted database users (source: https://aws.amazon.com/security/security-bulletins/2026-182-aws/)
CISA KEV: CVE-2026-126793 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126793 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://aws.amazon.com/security/security-bulletins/2026-182-aws/
- https://github.com/aws/aws-advanced-go-wrapper/releases/tag/release-2026-07-29
- https://github.com/aws/aws-advanced-go-wrapper/security/advisories/GHSA-fhr2-6r5v-gm9f
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126793
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126793"}.