You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
On Azure-sdk-bom version 1.3.9: several CVE's on dependencies #50905
Candidate labels considered: Client + Core (azure-core, which pulls in reactor-core/netty), Client + Azure Core netty/http-netty transport. Neither is clearly named; "version 1.3.9" doesn't identify an artifact, and the CVEs are in third-party dependencies (reactor, netty).
Confidence blockers: No specific Azure SDK package or /sdk/ path is named; multiple service labels are plausible, so exactly one can't be chosen confidently.
Outcome: Requested needs-triage — could not confidently predict labels.
👥 Owner Routing
CODEOWNERS scan: Not performed, because needs-triage was requested and the owner lookup steps were skipped.
Matched entry: none
Owners found: none
Outcome: Manual routing needed once the affected package is identified.
changed the title [-]On version 1.3.9: several CVE's on dependencies[/-][+]On Azure-sdk-bom version 1.3.9: several CVE's on dependencies[/+]on Oct 22, 2026
Activity
github-actions commentedon Oct 21, 2026
🎯 Agentic Issue Triage — Needs Manual Review
🏷️ Label Decision
👥 Owner Routing
[-]On version 1.3.9: several CVE's on dependencies[/-][+]On Azure-sdk-bom version 1.3.9: several CVE's on dependencies[/+]jairmyree commentedon Oct 27, 2026
Hello avpragana, these dependencies will be updated in the upcoming release of the BOM.