Skip to content

[GHSA-469j-vmhf-r6v7] Correct NLTK affected and fixed versions - #9207

Open
luis63e wants to merge 1 commit into
github:luis63e/advisory-improvement-9207from
luis63e:fix/ghsa-469j-vmhf-r6v7
Open

[GHSA-469j-vmhf-r6v7] Correct NLTK affected and fixed versions#9207
luis63e wants to merge 1 commit into
github:luis63e/advisory-improvement-9207from
luis63e:fix/ghsa-469j-vmhf-r6v7

Conversation

@luis63e

@luis63e luis63e commented Aug 26, 2026

Copy link
Copy Markdown

Summary

Correct the affected range for GHSA-469j-vmhf-r6v7 by replacing last_affected: 3.9.2 with fixed: 3.9.4.

The current record treats every version after 3.9.2 as unaffected. NLTK 3.9.3 still accepts parent-directory references in downloader package metadata, while 3.9.4 is the first release that rejects them.

Evidence

The upstream advisory identifies 3.9.4 as the patched version:

The validation was introduced by the upstream fix commit, which is absent from 3.9.3 and included in 3.9.4:

Both releases are published on PyPI:

A controlled constructor-level check using isolated installations produced:

NLTK version Result for subdir="../../tmp"
3.9.2 Accepted, builds ../../tmp/safe.zip
3.9.3 Accepted, builds ../../tmp/safe.zip
3.9.4 Rejected with ValueError

This check exercises the vulnerable metadata validation boundary without downloading or writing a file.

Validation

  • python3 -m json.tool: passed
  • Current OSV JSON schema validation: passed
  • git diff --check: passed

Change

One file: advisories/github-reviewed/2026/03/GHSA-469j-vmhf-r6v7/GHSA-469j-vmhf-r6v7.json

  • Update modified for this advisory revision.
  • Replace last_affected: 3.9.2 with fixed: 3.9.4 so 3.9.3 remains affected and 3.9.4 is recorded as the first fixed release.

@github-actions
github-actions Bot changed the base branch from main to luis63e/advisory-improvement-9207 August 26, 2026 01:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant