Skip to content

chore(ci): ignore disputed PYSEC-2025-183 in pip-audit#130

Merged
cipher813 merged 1 commit into
mainfrom
chore/pip-audit-ignore-pysec-2025-183
May 20, 2026
Merged

chore(ci): ignore disputed PYSEC-2025-183 in pip-audit#130
cipher813 merged 1 commit into
mainfrom
chore/pip-audit-ignore-pysec-2025-183

Conversation

@cipher813
Copy link
Copy Markdown
Owner

Summary

  • Daily scheduled pip-audit workflow began failing on main (4915af3) on 2026-05-20 when a new advisory, PYSEC-2025-183, landed in the OSV database against PyJWT 0.1.1–2.12.1 with no fix version.
  • The advisory flags that pyjwt doesn't enforce a minimum HMAC key length. Upstream disputes it: "the key length is chosen by the application that uses the library." 2.12.1 is the current latest release (2026-03-13); there is nothing to upgrade to.
  • mnemon's only pyjwt use is in src/mnemon/oauth_as.py, which signs and verifies with RS256 against a 2048-bit RSA keypair, algorithm hard-locked, no HS-allowance. The advisory describes no condition that applies to this usage.
  • Adds --ignore-vuln PYSEC-2025-183 to the workflow with the rationale inline, exactly as the existing workflow comment prescribes for no-fix advisories. Any new advisory on any dep still fails the workflow.

Test plan

  • CI pip-audit job goes green on this PR.
  • No other CI checks regress.
  • After merge, the daily scheduled run at 14:00 UTC stays green until the next genuinely actionable advisory.

🤖 Generated with Claude Code

PyJWT 2.12.1 (current latest) is flagged by PYSEC-2025-183 for not
enforcing a minimum HMAC key length. Upstream disputes the advisory
("the key length is chosen by the application that uses the
library") and no patched version exists. mnemon's only pyjwt use is
`src/mnemon/oauth_as.py`, which signs/verifies with RS256 against a
2048-bit RSA keypair — algorithm hard-locked, no HS-allowance — so
the advisory describes no condition that applies here.

Adds `--ignore-vuln PYSEC-2025-183` with the rationale inline next
to the existing workflow comment that prescribes this exact pattern
for no-fix advisories. Daily scheduled run on main went green-then-
red on 2026-05-20 as the advisory landed in the OSV database; this
restores the workflow without weakening the audit (any new advisory
on any dep still fails it).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@cipher813 cipher813 merged commit 08c2cb7 into main May 20, 2026
9 checks passed
@cipher813 cipher813 deleted the chore/pip-audit-ignore-pysec-2025-183 branch May 20, 2026 17: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