Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"schema_version": "1.4.0",
"id": "GHSA-6fmv-xxpf-w3cw",
"modified": "2026-03-27T19:40:25Z",
"modified": "2026-03-27T19:40:26Z",
"published": "2026-03-25T18:31:55Z",
"aliases": [
"CVE-2025-67030"
Expand Down Expand Up @@ -31,6 +31,28 @@
"database_specific": {
"last_known_affected_version_range": "<= 4.0.2"
}
},
{
Comment on lines 31 to +35
Copy link

Copilot AI Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the current data, the first affected entry uses introduced: 0 and fixed: 4.0.3, which implies all versions < 4.0.3 are vulnerable (including 3.6.1). Adding a second affected entry fixed at 3.6.1 won’t prevent 3.6.1 from still being flagged as affected by the first range. Please restructure the ranges so they’re non-overlapping (e.g., 3.x affected until 3.6.1, and 4.x affected from the first 4.x vulnerable release until 4.0.3), and adjust last_known_affected_version_range values to match.

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot Fix it as you understand what I was attenting to do.

"package": {
"ecosystem": "Maven",
"name": "org.codehaus.plexus:plexus-utils"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "3.6.1"
}
]
}
],
"database_specific": {
"last_known_affected_version_range": "<= 3.6.0"
}
}
],
"references": [
Expand Down
Loading