Skip to content

docs(agents): an unpublished dependency vulnerability stays private - #2145

Merged
ccoltx merged 1 commit into
mainfrom
polyglot/issue-classification-unpublished-deps
Nov 18, 2026
Merged

ccoltx merged 1 commit into
mainfrom
polyglot/issue-classification-unpublished-deps

Conversation

@polyglotAI-bot

@polyglotAI-bot polyglotAI-bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Follow-up to #2142 (merged). Review finding (Cursor Bugbot on ClickHouse/clickhouse-odbc#615, discussion r4619349461): the classification keeps every unpublished dependency vulnerability private, but the priority rule rated one in code that the client does not call as a public dependency update ("Cosmetic, docs, feature"), so triage could leave unpublished details on a public issue.

  • Classification: the impact Security names "a published one (CVE or GHSA) in code that the client calls, and any one that is not published yet". The list of "A vulnerability that is not public yet" says that an unpublished dependency vulnerability counts also in code that the client does not call.
  • Priority: a dependency vulnerability uses "Wrong data or security" when the client calls the vulnerable code, else "Cosmetic, docs, feature". A published one then asks for a dependency update in public; an unpublished one stays private also then, and the level is the proposed severity of the private report.

The other client repositories get the same text. No library code changes, so there is no changelog entry.

🤖 Generated with Claude Code


Note

Low Risk
Documentation-only updates to agent skill files; no runtime, auth, or data-handling code changes.

Overview
Aligns agent triage docs so unpublished dependency vulnerabilities stay private even when the vulnerable code is not on the client’s call path.

In issue-classification, the Security impact table now treats dependency issues as: published CVE/GHSA only when the client calls the vulnerable code, and any unpublished dependency vuln as Security. The “not public yet” checklist explicitly includes unpublished dependency vulns including code the client does not call.

In issue-priority, dependency vulns still map to “Wrong data or security” when the client calls the code and “Cosmetic, docs, feature” when it does not—but published cases are the public dependency-update path, while unpublished ones remain private with that severity used only as the proposed level in a private vulnerability report (cross-ref to the private-report section).

Reviewed by Cursor Bugbot for commit 8e97e9e. Bugbot is set up for automated code reviews on this repo. Configure here.

Review feedback (Bugbot on clickhouse-odbc#615): the classification kept
every unpublished dependency vulnerability private, but the severity rule
rated one in code that the client does not call as a public dependency
update. Now an unpublished one stays private also then; the low level
is only the proposed severity of the private report.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@polyglotAI-bot
polyglotAI-bot requested review from a team and kavirajk as code owners November 18, 2026 19:25

@security-ai-gate-reviewer security-ai-gate-reviewer 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.

Auto-approved by the AI review gate on 8e97e9e. Details in the approver's comment on this pull request.

@security-ai-gate-reviewer

Copy link
Copy Markdown

AI review gate — auto-approved

8e97e9e477ce is approved by security-ai-gate-reviewer[bot], an automated identity, not a human. The approval stands on the required AI review: Cursor Bugbot concluded green on this commit and the AI review gate is SUCCESS (its own comment has the verdict), and the change touches no path that requires a human reviewer. It is bound to this commit: a new push dismisses it and the approver re-evaluates.

History (latest 5 heads, newest first)

  • 8e97e9e477ce approved — green: Cursor Bugbot

@ccoltx
ccoltx merged commit 5f65ec2 into main Nov 18, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants