Nexus Void Research
Dependabot, Dependency Vulnerabilities, SCA, Vulnerability Prioritization, EPSS, CISA KEV, VEX, How-to
How to Resolve Dependabot Alerts and Cut the Noise (2026)
How to resolve Dependabot alerts: prioritize by exploitability, merge security updates, fix transitive deps, dismiss with reasons, stop the refill.
To resolve Dependabot alerts, open the repository's Security tab, sort alerts by what is exploited and reachable rather than by severity, and fix each one by merging Dependabot's security-update pull request, upgrading the parent dependency, or pinning a patched version. Alerts close automatically once the default branch no longer contains the vulnerable version. Dismiss the rest with a recorded reason, never silently.
Dependabot alerts are GitHub's notifications that a dependency in your repository has a known vulnerability. They are easy to switch on and easy to drown in: a repository with a few hundred dependencies can show dozens of alerts within days, many in transitive packages your code never calls. This guide shows how to clear the backlog, how to choose what to fix first, and how to stop it refilling.
How do Dependabot alerts work?
Dependabot reads the manifests and lockfiles on your default branch, builds a dependency graph, and matches each package version against the GitHub Advisory Database. Each match becomes an alert with a severity, the vulnerable version range, the first patched version and the manifest that brought it in.
Three related features are easy to confuse:
Feature | What it does |
|---|---|
Dependabot alerts | Tells you a dependency is vulnerable |
Dependabot security updates | Opens a pull request that upgrades the vulnerable dependency to the minimum patched version |
Dependabot version updates | Opens pull requests to keep dependencies current, vulnerable or not, on a schedule you set in |
An alert closes itself when a later scan of the default branch no longer finds the vulnerable version. You do not need to close fixed alerts by hand.
Step 1: Turn on security updates
If you only have alerts, every fix is manual. Turn on Dependabot security updates in the repository settings under code security, and Dependabot will open a pull request for each alert that has a patched version available.
To stop one pull request per package from flooding the queue, group them in .github/dependabot.yml:
One grouped pull request per ecosystem is much easier to review and test than twenty separate ones.
Step 2: Prioritize by exploitability, not severity
The default view sorts by severity, and a large share of alerts are rated High or Critical. That makes severity a weak sort key. In our 2026 vulnerability statistics, 55.2% of CVEs with a CVSS v3 severity are High or Critical, while only 0.44% of scored CVEs are confirmed exploited in the CISA Known Exploited Vulnerabilities catalog.
Sort your alerts with four questions instead:
Is it exploited? Check the CVE against the CISA KEV catalog. If it is listed, fix it first.
Is it likely to be exploited? Check its FIRST EPSS score, the estimated probability of exploitation in the next 30 days.
Does your code reach it? If production code never imports the vulnerable package, the alert is lower risk. If it only runs in tests or builds, lower again.
Is the service exposed? An internet-facing API outranks an internal batch job.
More detail in how to prioritize vulnerabilities with CVSS, EPSS and KEV.
Step 3: Merge the security-update pull requests
For alerts with a Dependabot pull request, the fix is usually one review away:
Read the release notes linked in the pull request, especially for minor and major bumps.
Let CI run. A green build with real tests is the main safety check.
Merge, and the alert closes on the next default-branch scan.
If CI fails, the patched version probably changed behaviour your code depends on. Fix forward in the same branch rather than closing the pull request and leaving the alert open.
Step 4: Fix alerts Dependabot cannot
Dependabot cannot open a pull request when the patched version conflicts with another dependency's requirements, when the vulnerable package is transitive and its parent has no fixed release, or when no patched version exists. For those:
Upgrade the parent package that pulls in the vulnerable one, if a newer parent ships the fix.
Pin the transitive package to a patched version with your package manager's override mechanism (
overridesin npm,resolutionsin Yarn,pnpm.overridesin pnpm, a constraints file or direct pin in Python).Replace or remove the package if it is abandoned.
Our walkthrough of fixing npm audit vulnerabilities shows the override approach step by step.
Step 5: Dismiss with a reason, not in bulk
Some alerts genuinely do not need a fix. GitHub's dismissal reasons cover the common cases:
Dismissal reason | Use it when |
|---|---|
A fix has already been started | The upgrade is in an open pull request |
No bandwidth to fix this | You accept the risk for now; set a review date |
Risk is tolerable to this project | The flaw cannot be triggered in how you use the package |
This alert is inaccurate or incorrect | The advisory does not apply to the version or ecosystem you use |
Vulnerable code is not actually used | Your code never reaches the vulnerable function or package |
Always add a comment with the evidence, such as "only used by the test runner" or "we never pass user input to this parser". A dismissed alert with no reason is indistinguishable from an ignored one at audit time. For a customer-facing record, publish the same decision as a VEX statement, which says machine-readably that a CVE does not affect your product and why.
Step 6: Use auto-triage rules for known noise
Dependabot auto-triage rules can automatically dismiss or snooze alerts that match conditions you define, such as low-severity alerts in development-only dependencies. Use them for noise you have already decided to accept, and review the rules each quarter so they do not hide something important.
Step 7: Stop the backlog from refilling
Keep version updates on so dependencies do not drift years behind, which turns every security fix into a risky major upgrade.
Require CI to pass before merging dependency pull requests, and keep tests meaningful.
Block new vulnerable dependencies at review time, so a pull request that adds a known-vulnerable package is caught before merge, not after.
Track the age of open alerts, not just the count. An alert open for a year is security debt; in 2026, 82% of organizations carry it, according to Veracode's State of Software Security report. See our AppSec backlog analysis.
How does ARGUS help clear Dependabot alerts?
Dependabot tells you a dependency is vulnerable. ARGUS tells you which of those vulnerabilities matter in your code, then writes the fix.
Reachability with evidence. For JavaScript, TypeScript and Python, ARGUS checks whether your source imports each vulnerable package and marks the finding reachable, unreachable or unknown, with an evidence string you can paste into a dismissal comment.
One priority score. Each finding gets a 0 to 100 score that blends CVSS, EPSS, CISA KEV and reachability, so a reachable, actively exploited CVE rises to the top and an unreachable one sinks without disappearing.
VEX, generated for you. Unreachable findings become VEX "not affected" statements in OpenVEX or CycloneDX format, which turns "we dismissed it" into a record auditors and customers can read.
Fix pull requests that are verified. Click Assign to Agent and ARGUS generates the smallest fix, verifies it with a build and a re-scan, and opens a pull request for you to review and merge. It never merges on its own.
Malicious package checks that advisories miss, against OSV's malicious-package feed plus a typosquat check on popular package names.
Limits: reachability is import-level and covers JS/TS and Python; Go, Maven, Cargo and RubyGems findings are treated as reachable. Java and .NET lockfiles are not yet advisory-matched. Read more about ARGUS SCA with reachability, or scan a repository free.
Frequently asked questions
How do I resolve Dependabot alerts?
Fix the vulnerable dependency on the default branch: merge Dependabot's security-update pull request, upgrade the parent package, or pin a patched version with an override. The alert closes automatically once the vulnerable version is gone. If no fix is needed, dismiss it with a reason and a comment explaining the evidence.
Do Dependabot alerts close automatically?
Yes. When a later scan of the default branch no longer finds the vulnerable version in your manifests or lockfiles, the alert is closed as fixed. You only need to act manually to dismiss alerts you have decided not to fix.
What is the difference between Dependabot alerts and Dependabot security updates?
Alerts tell you a dependency has a known vulnerability. Security updates go further and open a pull request that upgrades the dependency to the minimum patched version. Alerts work on their own; security updates need to be turned on separately in the repository settings.
Why can't Dependabot create a pull request for an alert?
Usually because no patched version exists yet, the patched version conflicts with another dependency's version requirements, or the vulnerable package is transitive and its parent has not released a fix. Upgrade the parent, pin the transitive package with an override, or replace it.
Which Dependabot alerts should I fix first?
Fix alerts for CVEs in the CISA Known Exploited Vulnerabilities catalog first, then those with high EPSS scores, then raise or lower each by whether your production code reaches the vulnerable package and whether the service is internet-facing. Severity alone marks too many alerts as urgent to be useful.
Is it safe to dismiss Dependabot alerts?
Yes, if you record why. Use the matching dismissal reason, such as vulnerable code not actually used or risk tolerable, and add a comment with the evidence. Avoid bulk-dismissing without reasons, because you lose the audit trail and may hide a real risk.
How do I group Dependabot pull requests?
Add a groups block to .github/dependabot.yml for each package ecosystem, with applies-to: security-updates and a pattern such as "*". Dependabot then opens one grouped pull request per ecosystem instead of one per package, which is easier to review and test.
How do I reduce Dependabot alert noise?
Prioritize by exploitability and reachability rather than severity, keep version updates on so fixes stay small, use auto-triage rules for development-only and low-severity noise you have accepted, and block new vulnerable dependencies at pull request review so the backlog does not refill.
DATA SOURCES
CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog ; FIRST EPSS: https://www.first.org/epss/ ; Veracode SoSS 2026 via Help Net Security