SkillVaultskills Browse all 500 skills

Security · Version 1.4.0 · Reviewed 2026-08-02

Dependency Vulnerability Triager

Find and prioritize exploitable risk in CVE prioritization and reachability analysis with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Prioritizes dependency advisories by reachability, exploit preconditions, deployed versions, exposure, compensating controls, and upgrade risk.

₹99 one-time

Get this skill archive

What this skill helps you do

  • CVE prioritization
  • Reachability analysis
  • Upgrade planning

How Dependency Vulnerability Triager works

You provide

Code, configuration, and the deployment trust model

It inspects

Reachable input-to-sink paths for CVE prioritization

It decides

A reachability analysis finding ranked by blast radius

You verify

Re-attempt the exploit path after remediation

What it checks first

Dependency Vulnerability Triager prioritizes dependency advisories by reachability, exploit preconditions, deployed versions, exposure, compensating controls, and upgrade risk. Use it when the work involves CVE prioritization, Reachability analysis, Upgrade planning.

  1. Trust boundaries and every point where untrusted input crosses one.
  2. Where authorization is enforced relative to where data is accessed.
  3. Secret handling: creation, storage, transmission, rotation, and revocation.
  4. What an attacker gains at each step, which determines whether a finding is material.

Failure modes it recognizes

  • Authorization enforced at the perimeter while internal callers reach the same data unchecked.
  • A single unparameterized query path among many parameterized ones.
  • Sensitive values written to logs or error responses.
  • A dependency vulnerability that is reachable in one code path and unreachable in the rest.

Answers it will reject

  • Reporting theoretical findings as exploitable without a demonstrated path.
  • Blocking a payload signature instead of removing the vulnerability class.
  • Treating obscurity as a control, which delays discovery without preventing exploitation.

Decision rules it applies

  • Prioritize by reachability and blast radius, not by scanner severity.
  • Fail closed on any ambiguity in an access decision.
  • Prefer eliminating the capability over sanitizing input into it.

Evidence it asks for

  • Trace input to sink and name every file and function on the path.
  • Verify the fix by attempting the original exploit path.
  • Check logs for prior exploitation before closing a finding.

The method inside

  1. Establish what is actually true about CVE prioritization from the supplied evidence, and mark what is missing.
  2. Identify the mechanism behind reachability analysis rather than restating the symptom.
  3. Choose the smallest defensible change for upgrade planning, weighing impact, confidence, effort, and reversibility.
  4. Recommend defense-in-depth and verification

Deliverables

  • CVE prioritization assessment
  • Reachability analysis decision and action plan
  • Upgrade planning verification checklist

Evidence requirements

  • Code, configuration, data flows, and trust boundaries
  • Identity, authorization, and deployment context
  • Threat model, controls, and known assumptions

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We received 140 dependency alerts overnight. Which ones should block today’s release?

Expected output

Only four affect code paths present in the production artifact, and one is remotely reachable before authentication. Prioritize that critical parser flaw; the build-time packages are not runtime exposure...

Boundaries and compatibility

Ideal for

  • CVE prioritization: produce a decision or artifact grounded in supplied evidence.
  • Reachability analysis: produce a decision or artifact grounded in supplied evidence.
  • Upgrade planning: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Authorizing offensive actions against systems without permission
  • Reporting theoretical issues as exploitable without a path

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.