π‘οΈ Sentinel: [HIGH] Fix libvips vulnerabilities in sharp#31
π‘οΈ Sentinel: [HIGH] Fix libvips vulnerabilities in sharp#31AstroMyth101 wants to merge 1 commit into
Conversation
Overrides sharp dependency version to address CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, and CVE-2026-35591 vulnerabilities. Co-authored-by: AstroMyth101 <75667958+AstroMyth101@users.noreply.github.com>
|
π Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a π emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
π¨ Severity: HIGH
π‘ Vulnerability:
sharpversions <0.35.0 have known vulnerabilities originating inlibvips(CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591) which were reported bypnpm audit.π― Impact: Potential exploitation of these vulnerabilities could lead to remote code execution (RCE) or denial of service (DoS) when processing malicious images.
π§ Fix: Added a
pnpm.overridesfield inpackage.jsonto force the resolution ofsharpto a secure version (0.35.3). Updatedpnpm-lock.yamland.jules/sentinel.mdjournal with learning.β Verification: Verified by running
pnpm auditwhich now reports 0 vulnerabilities, and runningpnpm buildto ensure the project still builds correctly.PR created automatically by Jules for task 12808174257597323717 started by @AstroMyth101