AWS SDK for pandas 3.17.1 Fixes Iceberg SQL Identifier Injection
Tech GuruQuick Answer
Upgrade awswrangler to 3.17.1 or later and patch forks. Review who can edit Glue table metadata used by privileged to_iceberg() jobs; the earlier patch date does not change the November 2 advisory release.
Confirm Scope And Apply The Supported Remediation
What to do now: Record awswrangler versions, to_iceberg jobs, Glue metadata editors, execution roles and table permissions. Match the documented versions, enabled features and attack prerequisites to the deployment before assigning applicability. Upgrade to 3.17.1 or later. Until then, avoid a writer more privileged than metadata editors and restrict glue:UpdateTable and related permissions; AWS states there is no complete workaround. Verify deployed dependencies, test Iceberg writes and access boundaries, and retain relevant Glue changes, job logs and change evidence.
Last verified: 2026-11-02 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | AWS SDK for pandas (awswrangler), Apache Iceberg write component |
|---|---|
| Advisory | 2026-161-AWS |
| CVE | CVE-2026-119301 |
| Authoritative release date | 2026-11-02 16:30:00 UTC |
| Authority revision date | No separate revision date is stated in the initial AWS bulletin. |
| Affected versions | awswrangler 3.5.2 and later before 3.17.1, where a less-privileged principal can modify Glue Data Catalog metadata consumed by a more-privileged writer. |
| Fixed version | awswrangler 3.17.1 or later; the fix was released August 3, 2026 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | The cited authority does not state that this issue is being maliciously exploited.; no exploitation claim is inferred. |
Authority-Specific Scope And Version Evidence
| Publication and fix | Published November 2, 2026 at 08:30 PST (16:30 UTC); fixed library released August 3, 2026. |
|---|
What Changed
AWS published a bulletin for SQL identifier quoting that can let a metadata editor read tables accessible to a more-privileged writer and write to that writer’s target table.
What To Validate Now
- Inventory. Record awswrangler versions, to_iceberg jobs, Glue metadata editors, execution roles and table permissions.
- Establish applicability. Match the documented versions, enabled features and attack prerequisites to the deployment before assigning applicability.
- Remediate. Upgrade to 3.17.1 or later. Until then, avoid a writer more privileged than metadata editors and restrict glue:UpdateTable and related permissions; AWS states there is no complete workaround.
- Validate. Verify deployed dependencies, test Iceberg writes and access boundaries, and retain relevant Glue changes, job logs and change evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Do not infer exposure from using pandas or Glue alone. Review role separation and forked code; AWS provides no CVSS score in this bulletin.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
