Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

jina-ai/serve
master @ 0f32b2a
7
Fixes
5
CVEs
CRITICAL
Peak severity
Highlights
Denial of Service: 3 prior fixes. Scrutinize any change in this area.
CI/CD: most-fixed (1 issue). Treat as high-risk during review.
4 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Deserialization: The executor YAML loading process bypassed original sanitization steps, requiring robust regex tag blocking to prevent unsafe YAML deserialization and remote code execution during executor initialization.
Credential Exposure: Hardcoded binary-encoded Docker Hub credentials present in helper files posed a severe static credential exposure risk, requiring transition to runtime-resolved credentials.
Unsafe GitHub Actions Workflow Execution: Forks of the pull request workflow could execute code-injection and styling checks with access to privileged secrets if conditions are not explicitly gated at the step level.