[GHSA-6q48-6c7w-9gw2] certifi bundles emSign root CAs with compromised intermediate CA keys by nemo-lm · Pull Request #10465 · github/advisory-database · GitHub
Skip to content

[GHSA-6q48-6c7w-9gw2] certifi bundles emSign root CAs with compromised intermediate CA keys - #10465

Open
nemo-lm wants to merge 1 commit into
nemo-lm/advisory-improvement-10465from
nemo-lm-GHSA-6q48-6c7w-9gw2
Open

nemo-lm wants to merge 1 commit into
nemo-lm/advisory-improvement-10465from
nemo-lm-GHSA-6q48-6c7w-9gw2

Conversation

@nemo-lm

@nemo-lm nemo-lm commented Oct 21, 2026

Copy link
Copy Markdown

Updates

  • Affected products
  • Description

Comments
As per upstream guidance, 2026.10.18
should be considered the patched version, with a preferred upgrade to 2026.10.19. Any users running 2026.10.18 should not get an alert.

@github

github commented Oct 21, 2026

Copy link
Copy Markdown
Collaborator

Copilot AI max review requested due to automatic review settings October 21, 2026 12:30
@github-actions
github-actions Bot changed the base branch from main to nemo-lm/advisory-improvement-10465 October 21, 2026 12:31

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

Upstream commits confirm the corrected fixed-version boundary, and no blocking issues remain.

1 open issue
What changed in this PR

Updates certifi’s security advisory so users running 2026.10.18 no longer receive vulnerability alerts.

Changes:

  • Sets 2026.10.18 as the first fixed version.
  • Revises upgrade guidance to prefer 2026.10.19 and updates metadata.
File Description
advisories/​github-reviewed/​2026/​10/​GHSA-6q48-6c7w-9gw2/​GHSA-6q48-6c7w-9gw2.json Corrects the affected range and revises remediation guidance.

Review effort: Max

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Guidance should still mention .19 preferably imo.

Upgrade to 2026.10.18 or later, preferably 2026.10.19 or later,

is just bad wording.

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.

3 participants