AAP-64830: fixes CVE-2026-1207, CVE-2026-1287, CVE-2026-1312.#1834
Merged
AAP-64830: fixes CVE-2026-1207, CVE-2026-1287, CVE-2026-1312.#1834
Conversation
Django: SQL Injection via RasterField band index parameter
pip-audit has an older version of `pip` which causes it to fail due to https://www.cve.org/CVERecord?id=CVE-2026-1703.
de1987
approved these changes
Feb 6, 2026
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira Issue: https://issues.redhat.com/browse/AAP-64830
Jira Issue: https://issues.redhat.com/browse/AAP-64841
Jira Issue: https://issues.redhat.com/browse/AAP-64845
Description
Handles the following issues:
Testing
Steps to test
Type of Change
Backport Policy
This change should be:
Automated Backport Instructions
After this PR is merged, add one or more labels to automatically create backport PRs:
backport/stable-2.4- Backport to stable-2.4 branchbackport/stable-2.5- Backport to stable-2.5 branchbackport/stable-2.6- Backport to stable-2.6 branchbackport/all- Backport to all active stable branchesno-backport- Explicitly mark as not needing backportBackport Justification
Special backport considerations:
Scenarios tested
Production deployment