fix: ignore diffusers GHSA-98h9-4798-4q5v in pip-audit

[timzsu]

Purpose

Silence pip-audit on GHSA-98h9-4798-4q5v (CVE-2026-44513, HIGH, CVSS 8.8) in diffusers==0.36.0. Same upgrade blocker as the already-ignored GHSA-j7w6-vpvq-j3gm — both are fixed in diffusers 0.38.0, which requires safetensors>=0.8.0rc0 pre-release that uv lock won't pick up without an explicit opt-in.

Changes

• .github/workflows/security.yml — add --ignore-vuln GHSA-98h9-4798-4q5v to both pip-audit blocks (worker CPU and worker GPU delta).
• docs/CODE_STYLE.md — add a row in the ignored-CVE table referencing the same blocker as the existing diffusers row.

Design

The advisory is a trust_remote_code=False bypass in DiffusionPipeline.from_pretrained via custom_pipeline= (cross-repo or local-snapshot variants) or local snapshots whose model_index.json references custom-component .py files. The DiffusersExecutor calls AutoPipelineForText2Image.from_pretrained(ident, **load_kwargs) with a Hub identifier (no local path), no custom_pipeline= argument, and trust_remote_code=True only when the workflow explicitly opts in via spec.model_trust_remote_code. The advisory variants 1 and 2 are unreachable; variant 3 (HF cache snapshot with custom components) is theoretically reachable but bounded by the workflow author's existing trust scope (they can already set model_trust_remote_code=True).

Bumping to 0.38.0 is the only real fix per the advisory, but it pulls in a safetensors pre-release. Track the blocker on the GHSA-j7w6-vpvq-j3gm row and drop both ignores together when the cap lifts.

Test Plan

CI.

Test Result

CI passes.

---

Pre-submission Checklist

• I have read the contribution guidelines.
• I have run pre-commit run --all-files and fixed any issues.
• I have added or updated tests covering my changes (if applicable).
• I have verified that uv run pytest tests/ passes locally.
• If I changed shared schemas or proto definitions, I have checked downstream compatibility across Server and Worker.
• If I changed the SDK or CLI, I have verified the affected packages work (uv sync --all-extras --frozen).
• If this is a breaking change, I have prefixed the PR title with [BREAKING] and described migration steps above.
• I have updated documentation or config examples if user-facing behavior changed.

[kaiitunnz]

LGTM.