Skip to content

Add upstream CVE detection to dependency-cve-monitor workflow - #7264

Open
bhoradc wants to merge 2 commits into
masterfrom
add-upstream-cve-monitor
Open

Add upstream CVE detection to dependency-cve-monitor workflow#7264
bhoradc wants to merge 2 commits into
masterfrom
add-upstream-cve-monitor

Conversation

@bhoradc

@bhoradc bhoradc commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Motivation and Context

Enhance the existing dependency-cve-monitor workflow with a new job that detects CVEs directly from upstream sources before they reach the global GitHub Advisory Database.

While we have Dependabot alerts, libraries like Apache HttpComponents have advisories that remain in unreviewed state — meaning Dependabot alerts never fire for them. This is a recent known limitation documented in this GitHub blog
post
. This change adds an upstream check for early detection.

Changes

  • New check-upstream-advisories job added to dependency-cve-monitor.yml
  • Checks Netty and Jackson via GitHub repo-level security advisories API
  • Checks Apache HttpComponents via NVD + cve.org (no repo advisories exist for Apache)
  • Filters by SDK-used packages and compares patched versions against SDK's current versions
  • Sends Slack notification with affected CVEs and recommended upgrade target
  • Minor update to existing notify-alerts job: added source attribution and description to Slack message

Detection Sources

Library Source
Netty repos/netty/netty/security-advisories
Jackson repos/FasterXML/jackson-*/security-advisories
Apache NVD keyword search + cve.org structured data

Testing

Integration tested in a forked repo — validated positive detection (alerts when vulnerable), negative detection (silent when patched), version comparison logic, and PAT access. No new secrets or permissions required.

@bhoradc
bhoradc requested a review from a team as a code owner August 12, 2026 21:53
@bhoradc bhoradc added changelog-not-required Indicate changelog entry is not required for a specific PR no-api-surface-area-change Indicate there is no API surface area change and thus API surface area review is not required labels Aug 12, 2026
@bhoradc
bhoradc requested a review from zoewangg August 12, 2026 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog-not-required Indicate changelog entry is not required for a specific PR no-api-surface-area-change Indicate there is no API surface area change and thus API surface area review is not required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant