Skip to content

[Snyk] Fix for 2 vulnerabilities - #19

Open
RemyLoveLogicAI wants to merge 1 commit into
mainfrom
snyk-fix-c6a8208aa2141346f5d26ecef156a8de
Open

[Snyk] Fix for 2 vulnerabilities#19
RemyLoveLogicAI wants to merge 1 commit into
mainfrom
snyk-fix-c6a8208aa2141346f5d26ecef156a8de

Conversation

@RemyLoveLogicAI

@RemyLoveLogicAI RemyLoveLogicAI commented Feb 17, 2026

Copy link
Copy Markdown
Owner

User description

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • skyvern-frontend/package.json
  • skyvern-frontend/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Prototype Pollution
SNYK-JS-AXIOS-15252993
  225  
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-15268416
  61  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution
🦉 Allocation of Resources Without Limits or Throttling


Summary by cubic

Upgraded axios and express in skyvern-frontend to patch two vulnerabilities and keep runtime dependencies secure. Fixes Prototype Pollution in axios and a resource allocation risk via qs.

  • Dependencies
    • axios: ^1.6.8 → ^1.13.5 (fixes SNYK-JS-AXIOS-15252993)
    • express: ^4.19.2 → ^4.22.0 (brings qs 6.14.x, fixes SNYK-JS-QS-15268416)

Written for commit dfea534. Summary will update on new commits.


CodeAnt-AI Description

Upgrade frontend dependencies to secure versions to fix known vulnerabilities

What Changed

  • Updated axios to a later version that fixes a prototype pollution vulnerability and strengthens HTTP request handling
  • Updated qs (query string parser) to a patched version to prevent resource-exhaustion via crafted query strings
  • Upgraded Express and several Express-related packages to patched releases to use safer middleware versions and dependency trees

Impact

✅ Fewer dependency vulnerabilities
✅ Safer HTTP requests (fixed prototype pollution in axios)
✅ Lower risk of query-parsing resource exhaustion

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

@devloai

devloai Bot commented Feb 17, 2026

Copy link
Copy Markdown

Unable to trigger custom agent "Code Reviewer". You have run out of credits 😔
Please upgrade your plan or buy additional credits from the subscription page.

@safedep

safedep Bot commented Feb 17, 2026

Copy link
Copy Markdown

SafeDep Report Summary

Green Malicious Packages Badge Green Vulnerable Packages Badge Green Risky License Badge

Package Details
Package Malware Vulnerability Risky License Report
icon axios @ 1.13.5
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon body-parser @ 1.20.4
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon call-bind-apply-helpers @ 1.0.2
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon call-bound @ 1.0.4
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon cookie @ 0.7.2
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon dunder-proto @ 1.0.1
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon encodeurl @ 2.0.0
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon es-define-property @ 1.0.1
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon es-object-atoms @ 1.1.1
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon es-set-tostringtag @ 2.1.0
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon express @ 4.22.0
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon finalhandler @ 1.3.2
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon follow-redirects @ 1.15.11
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon form-data @ 4.0.5
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon get-intrinsic @ 1.3.0
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon get-proto @ 1.0.1
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon gopd @ 1.2.0
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon has-symbols @ 1.1.0
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon has-tostringtag @ 1.0.2
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon http-errors @ 2.0.1
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon math-intrinsics @ 1.1.0
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon merge-descriptors @ 1.0.3
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon object-inspect @ 1.13.4
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon path-to-regexp @ 0.1.12
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon qs @ 6.14.2
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon raw-body @ 2.5.3
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon send @ 0.19.2
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon serve-static @ 1.16.3
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon side-channel @ 1.1.0
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon side-channel-list @ 1.0.0
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon side-channel-map @ 1.0.1
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon side-channel-weakmap @ 1.0.2
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗
icon statuses @ 2.0.2
skyvern-frontend/package-lock.json
ok icon
ok icon
ok icon
🔗

This report is generated by SafeDep Github App

@haiec-compliance

Copy link
Copy Markdown

🛡️ HAIEC Attestation Readiness: -- → 30 (0)

Frameworks Evaluated: SOC2, ISO27001, PCI-DSS
Progress: ███░░░░░░░ 30%

HAIEC scans your repository for compliance evidence across multiple frameworks simultaneously.

⚠️ 6 Compliance Gaps Found

⚡ 2 HIGH across 3 frameworks

🟠 Missing code ownership documentation [HIGH]

Affects: ISO27001 · PCI-DSS

Why This Matters: PCI auditors will fail you immediately. Without documented access controls, you cannot prove that only authorized personnel can modify payment processing code.

How to Fix:

  1. Create CODEOWNERS with strict ownership rules
  2. Assign payment code to PCI-trained developers only
  3. Enable required reviews from code owners

📄 Ready-to-use template: Download CODEOWNERS →

⏱️ ~25 min to fix


🟠 Dependabot not enabled [HIGH]

Affects: SOC2 · ISO27001 · PCI-DSS

Why This Matters: Unpatched vulnerabilities in payment systems are a common cause of breaches. The Equifax breach happened because of an unpatched vulnerability. Don't be next.

How to Fix:

  1. Enable Dependabot immediately
  2. Set up alerts for critical vulnerabilities
  3. Document patch management SLA

📄 Ready-to-use template: Download dependabot.yml →

⏱️ ~10 min to fix


🟡 Missing CODEOWNERS file [MEDIUM]

Affects: SOC2 · ISO27001 · PCI-DSS

Why This Matters: Anyone with write access can push directly to production without review. A single developer could deploy malicious code, delete the entire codebase, or leak customer data with zero oversight.

How to Fix:

  1. Go to Settings > Branches > Add rule
  2. Branch name: main
  3. Enable: Require pull request reviews, Require status checks
  4. Save changes

⏱️ ~5 min to fix


📋 +3 more issues not shown. View complete report →

💡 Quick Wins: 2 issues fixable in ~10 minutes


💡 First scan complete. Showing top 3 priority items. View complete analysis →

🎯 Next Steps

  1. View Complete Report → - See all findings and recommendations
  2. Run Detailed Scan → - Get comprehensive compliance analysis
  3. Download Evidence Report → - Export for auditors

💡 Quick wins: Add the missing files shown above to improve your score to 100%


🔍 Free AI Code Security Scan

This scan checked repository metadata. Upgrade to AI Code Analysis (free for public repos) to scan your code for:

Category Examples
Prompt Injection User input reaching system prompts
Data Leakage PII/secrets in AI responses
Access Control Missing auth on AI endpoints
82+ AI Security Rules OWASP Top 10 for LLMs

Enable Free Code Analysis → | Learn More →


🚀 Accelerate Your Compliance with HAIEC

Tool What It Does Link
AI Security Scanner Scan AI/ML code for 91 security rules in minutes Start Scan →
Compliance Wizard Step-by-step SOC2, ISO27001, HIPAA, PCI-DSS readiness Launch Wizard →
Template Library Production-ready SECURITY.md, CODEOWNERS, CI configs Browse Templates →
Trust Artifacts Verifiable compliance badges for your README View Artifacts →

💡 Free tier available — scan unlimited public repos, generate trust artifacts, and export compliance evidence at no cost.


🤖 Automated by HAIEC — AI Compliance & Security Platform | Documentation | Support

@ai-document-creator

Copy link
Copy Markdown

ℹ️ No Configured Files to Document

This PR doesn't contain any files that match your documentation configuration.

Files Changed

  • ✏️ skyvern-frontend/package-lock.json
  • ✏️ skyvern-frontend/package.json

Why No Documentation?

None of the files configured to be watched in your .github/wai-docbot.yml have changed in this PR.

DocBot processes files based on:

  • Include patterns - Which file types/paths to document
  • Exclude patterns - Which files/folders to skip

Need to document these files?

Check your .github/wai-docbot.yml configuration:

  • Verify your include patterns cover the files you want documented
  • Check if any exclude patterns are blocking these files
  • Ensure file extensions are configured for documentation

View configuration guide →


If changes were expected but not processed, please review your configuration settings.

@codeant-ai

codeant-ai Bot commented Feb 17, 2026

Copy link
Copy Markdown

CodeAnt AI is reviewing your PR.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@coderabbitai

coderabbitai Bot commented Feb 17, 2026

Copy link
Copy Markdown

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch snyk-fix-c6a8208aa2141346f5d26ecef156a8de

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @RemyLoveLogicAI, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request provides an automated security update to resolve identified vulnerabilities within the project's npm dependencies. It specifically targets and remediates a high-severity Prototype Pollution issue in axios and a medium-severity resource allocation vulnerability in qs by upgrading these key packages and their associated transitive dependencies to more secure versions.

Highlights

  • Vulnerability Fixes: Addressed two security vulnerabilities: a high-severity 'Prototype Pollution' (SNYK-JS-AXIOS-15252993) in axios and a medium-severity 'Allocation of Resources Without Limits or Throttling' (SNYK-JS-QS-15268416) related to qs.
  • Dependency Upgrades: Updated direct dependencies axios from ^1.6.8 to ^1.13.5 and express from ^4.19.2 to ^4.22.0.
  • Automated Remediation: This pull request was automatically generated by Snyk to apply the necessary security patches and dependency updates.
Changelog
  • skyvern-frontend/package-lock.json
    • Updated axios and express to their new versions to reflect package.json changes.
    • Updated numerous transitive dependencies (e.g., body-parser, cookie, encodeurl, finalhandler, follow-redirects, form-data, get-intrinsic, gopd, has-symbols, http-errors, raw-body, send, serve-static, side-channel, statuses, type-is, unpipe).
    • Added new helper dependencies (call-bind-apply-helpers, call-bound, dunder-proto, es-object-atoms, es-set-tostringtag, get-proto, math-intrinsics, side-channel-list, side-channel-map, side-channel-weakmap).
    • Added license fields to many dependency entries.
    • Removed define-data-property and has-property-descriptors entries.
  • skyvern-frontend/package.json
    • Updated axios dependency to version ^1.13.5.
    • Updated express dependency to version ^4.22.0.
Activity
  • Snyk automatically created this pull request to fix identified vulnerabilities in the project's npm dependencies.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@bito-code-review

Copy link
Copy Markdown

Bito Automatic Review Skipped - Files Excluded

Bito didn't auto-review because all changed files are in the exclusion list. You can change the excluded files settings here, or contact the agent instance creator at jmjones925@gmail.com.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@codeant-ai codeant-ai Bot added the size:L This PR changes 100-499 lines, ignoring generated files label Feb 17, 2026
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​express@​4.19.2 ⏵ 4.22.097100 +110087100
Updatednpm/​axios@​1.6.8 ⏵ 1.13.597 -1100 +4010096100

View full report

@codeant-ai

codeant-ai Bot commented Feb 17, 2026

Copy link
Copy Markdown

CodeAnt AI finished reviewing your PR.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No issues found across 2 files

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request, automatically generated by Snyk, aims to fix two security vulnerabilities by updating axios and express dependencies. The update for express correctly addresses the vulnerability in qs. However, the target version for axios (1.13.5) appears to be a typo, as this version does not exist on npm. I've left a critical comment with a suggestion to update to a correct version that resolves the vulnerability and allows the project to build.

"@uiw/react-codemirror": "^4.23.0",
"@xyflow/react": "^12.1.1",
"axios": "^1.6.8",
"axios": "^1.13.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

security-critical critical

The new version for axios appears to be incorrect. Version 1.13.5 does not seem to exist on npm, which will likely cause the build to fail. The vulnerability mentioned in the pull request description, SNYK-JS-AXIOS-15252993 (Prototype Pollution), is fixed in axios version 1.7.0 and later. I suggest updating to the latest stable version, 1.7.2, to ensure the vulnerability is patched.

Suggested change
"axios": "^1.13.5",
"axios": "^1.7.2",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:L This PR changes 100-499 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants