chore(deps): [migrate-from-aws-to-google-cloud] Update dependency flask to v3.1.3 [SECURITY] - autoclosed#345
Closed
renovate-bot wants to merge 1 commit intoGoogleCloudPlatform:mainfrom
Conversation
forking-renovate
Bot
added
dependencies
renovate-bot
added
dependencies
…sk to v3.1.3 [SECURITY]
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/pypi-flask-vulnerability
branch
from
dd916d4 to
ce96e52
Compare
copybara-service Bot
pushed a commit
that referenced
this pull request
Mar 4, 2026
…sk to v3.1.3 [SECURITY] Import of github PR #345 from renovate-bot #345 This PR contains the following updates: [flask](https://redirect.github.com/pallets/flask): `==3.1.2` → `==3.1.3` ### GitHub Vulnerability Alerts #### [CVE-2026-27205](https://redirect.github.com/pallets/flask/security/advisories/GHSA-68rp-wp8r-4726) When the `session` object is accessed, Flask should set the `Vary: Cookie` header. This instructs caches not to cache the response, as it may contain information specific to a logged in user. This is handled in most cases, but some forms of access such as the Python `in` operator were overlooked. The severity depends on the application's use of the session, and the cache's behavior regarding cookies. The risk depends on all these conditions being met. 1. The application must be hosted behind a caching proxy that does not ignore responses with cookies. 2. The application does not set a `Cache-Control` header to indicate that a page is private or should not be cached. 3. The application accesses the session in a way that does not access the values, only the keys, and does not mutate the session. --- ### Flask session does not add `Vary: Cookie` header when accessed in some ways [CVE-2026-27205](https://nvd.nist.gov/vuln/detail/CVE-2026-27205) / [GHSA-68rp-wp8r-4726](https://redirect.github.com/advisories/GHSA-68rp-wp8r-4726) --- ### Release Notes --- ### Commit Message(s): -- Change 1 of 1 by Mend Renovate <bot@renovateapp.com>: chore(deps): [migrate-from-aws-to-google-cloud] Update dependency flask to v3.1.3 [SECURITY] GitOrigin-RevId: 55ea70df13da979a0b12bf84487b8abe1a5b8c2f Change-Id: Ic9ca02a05bb7aaefe31478374209cb237102d794
renovate-bot
changed the title
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.
This PR contains the following updates:
==3.1.2→==3.1.3GitHub Vulnerability Alerts
CVE-2026-27205
When the
sessionobject is accessed, Flask should set theVary: Cookieheader. This instructs caches not to cache the response, as it may contain information specific to a logged in user. This is handled in most cases, but some forms of access such as the Pythoninoperator were overlooked.The severity depends on the application's use of the session, and the cache's behavior regarding cookies. The risk depends on all these conditions being met.
Cache-Controlheader to indicate that a page is private or should not be cached.Flask session does not add
Vary: Cookieheader when accessed in some waysCVE-2026-27205 / GHSA-68rp-wp8r-4726
More information
Details
When the
sessionobject is accessed, Flask should set theVary: Cookieheader. This instructs caches not to cache the response, as it may contain information specific to a logged in user. This is handled in most cases, but some forms of access such as the Pythoninoperator were overlooked.The severity depends on the application's use of the session, and the cache's behavior regarding cookies. The risk depends on all these conditions being met.
Cache-Controlheader to indicate that a page is private or should not be cached.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
pallets/flask (flask)
v3.1.3Compare Source
Released 2026-02-18
but not the values, such as
inandlen. :ghsa:68rp-wp8r-4726Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.