[GHSA-v9v8-jp27-55gf] marimo before 0.23.15 contains a configuration injection... - #9189
Open
PercevalFox wants to merge 1 commit into
Open
Conversation
github-actions
Bot
changed the base branch from
main
to
PercevalFox/advisory-improvement-9189
August 23, 2026 01:51
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
1 participant
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.
Updates
Comments
This advisory is unreviewed and has no package mapping, so it does not surface to users of the affected package.
The repository marimo-team/marimo publishes the PyPI package
marimo.The advisory names the sanitize_pyproject_dict function and the base_url injection vector. The fix commit (1a21bd71, PR #10281, "additional pep 723 sanitization") modifies exactly that function in marimo/_config/reader.py to exclude ai/base_url, secrets and server keys from notebook-supplied config, with a regression test asserting a notebook's ai.open_ai.base_url must not override operator settings. This matches the advisory text.
I verified the boundary against the published PyPI wheels:
This matches the "before 0.23.15" wording in the description and the release tag already listed in the references (https://github.com/marimo-team/marimo/releases/tag/0.23.15).
Proposed range: introduced 0, fixed 0.23.15.
The CVSS v4 vector was rewritten to omit the trailing Not Defined (X) metrics, which the form's validator rejects. This is semantically identical per the CVSS v4.0 specification and does not change the severity assessment. CVSS v3 left untouched.
The advisory also had no title. The proposed one follows the database's naming convention and reflects the existing CWE-345 classification.