Improper neutralization of quoting syntax in Apache Iceberg SQL identifier generation in AWS SDK for pandas
Affects awswrangler 3.5.2 up to but not including 3.17.1 where a more privileged principal also calls to_iceberg() on the same table. Fixed in 3.17.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.17.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected awswrangler versions: 3.5.2 up to but not including 3.17.1 A more privileged principal invokes to_iceberg() on the affected table
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 3.17.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
AWS SDK for pandas (also published as awswrangler) has a flaw in how its Apache Iceberg write component builds SQL identifiers, which can allow a user who can modify AWS Glue Data Catalog metadata to read tables and write to tables that a more privileged principal can access, by using a specially crafted column name.
Read the original description
Improper neutralization of quoting syntax in SQL identifier construction in the Apache Iceberg write component in AWS SDK for pandas (also published as awswrangler) 3.5.2 through 3.17.0 might allow an authenticated remote user with permission to modify AWS Glue Data Catalog metadata to read any table that a separate, more privileged principal can access and write to the table that principal is updating via a crafted column name. To remediate this issue, users should upgrade to version 3.17.1 or later.
What to do
Check whether your setup matches what the bug needs.
Affected awswrangler versions: 3.5.2 up to but not including 3.17.1 A more privileged principal invokes to_iceberg() on the affected tableUpgrade to a fixed version: 3.17.1.
Workaround: Avoid calling to_iceberg() with a principal that has more privileges than the principals who can modify that table's AWS Glue Data Catalog metadata, and restrict glue:UpdateTable and related permissions on shared databases
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- AWS aws-sdk-pandas
From 3.5.2 · fixed in 3.17.1
Evidence 3
- Advisory
- Advisory
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119301
What does this mean?
An authenticated user can read any table that a more privileged principal can access through to_iceberg(), and can write to the table that principal is updating.Source: github.com
Am I affected, and how do I check?
Affected versions are awswrangler 3.5.2 up to but not including 3.17.1. The setup also requires a more privileged principal invoking to_iceberg() on the affected table; the installed version can be checked with pip show awswrangler.Source: github.com
What should I do about it?
Upgrade AWS SDK for pandas to version 3.17.1 or later, which contains the fix.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data