CVE-2026-11401

Aurora PostgreSQL is a fully managed relational database engine that's compatible with PostgreSQL.

An issue in Aurora PostgreSQL using the AWS Go Wrapper waa identified, see CVE-2026-11401.

Impact
An issue in AWS Wrappers for Amazon Aurora PostgreSQL may allow for privilege escalation to rds_superuser role. A low privilege authenticated user can create a crafted function that could be executed with permissions of other Amazon Relational Database Service (RDS) users.

Impacted versions: AWS Go Wrapper 2026-04-06

Patches
This issue has been addressed in AWS Go Wrapper 2026-05-26. Maintainers recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.

Workarounds
Remove the public schema from the search path.

References
If there are any questions or comments about this advisory, contact [AWS/Amazon] Security via the vulnerability reporting page or directly via email to [email protected]. Please do not create a public GitHub issue.

CVE-2026-11401 has a CVSS score of 8.0 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.0.1, 1.07, 1.1.2, 1.0.4, 1.1.1, 1.0.7); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-11401? CVE-2026-11401 is a high-severity security vulnerability in github.com/aws/aws-advanced-go-wrapper/awssql/v2 (go), affecting versions <= 2.0.0. It is fixed in 2.0.1, 1.07, 1.1.2, 1.0.4, 1.1.1, 1.0.7.
2. How severe is CVE-2026-11401? CVE-2026-11401 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-11401?
   • github.com/aws/aws-advanced-go-wrapper/awssql/v2 (go) (versions <= 2.0.0)
   • github.com/aws/aws-advanced-go-wrapper/xray (go) (versions <= 1.06)
   • github.com/aws/aws-advanced-go-wrapper/aws-secrets-manager (go) (versions <= 1.1.1)
   • github.com/aws/aws-advanced-go-wrapper/custom-endpoint (go) (versions <= 1.0.3)
   • github.com/aws/aws-advanced-go-wrapper/federated-auth (go) (versions <= 1.1.0)
   • github.com/aws/aws-advanced-go-wrapper/iam (go) (versions <= 1.1.0)
   • github.com/aws/aws-advanced-go-wrapper/mysql-driver (go) (versions <= 1.1.0)
   • github.com/aws/aws-advanced-go-wrapper/okta (go) (versions <= 1.1.0)
   • github.com/aws/aws-advanced-go-wrapper/pgx-driver (go) (versions <= 1.1.0)
   • github.com/aws/aws-advanced-go-wrapper/otlp (go) (versions <= 1.0.6)
   • github.com/aws/aws-advanced-go-wrapper/auth-helpers (go) (versions <= 1.1.0)
4. Is there a fix for CVE-2026-11401? Yes. CVE-2026-11401 is fixed in 2.0.1, 1.07, 1.1.2, 1.0.4, 1.1.1, 1.0.7. Upgrade to this version or later.
5. Is CVE-2026-11401 exploitable, and should I be worried? Whether CVE-2026-11401 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-11401 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-11401?
   • Upgrade github.com/aws/aws-advanced-go-wrapper/awssql/v2 to 2.0.1 or later
   • Upgrade github.com/aws/aws-advanced-go-wrapper/xray to 1.07 or later
   • Upgrade github.com/aws/aws-advanced-go-wrapper/aws-secrets-manager to 1.1.2 or later
   • Upgrade github.com/aws/aws-advanced-go-wrapper/custom-endpoint to 1.0.4 or later
   • Upgrade github.com/aws/aws-advanced-go-wrapper/federated-auth to 1.1.1 or later
   • Upgrade github.com/aws/aws-advanced-go-wrapper/iam to 1.1.1 or later
   • Upgrade github.com/aws/aws-advanced-go-wrapper/mysql-driver to 1.1.1 or later
   • Upgrade github.com/aws/aws-advanced-go-wrapper/okta to 1.1.1 or later
   • Upgrade github.com/aws/aws-advanced-go-wrapper/pgx-driver to 1.1.1 or later
   • Upgrade github.com/aws/aws-advanced-go-wrapper/otlp to 1.0.7 or later
   • Upgrade github.com/aws/aws-advanced-go-wrapper/auth-helpers to 1.1.1 or later