CVE not assigned for 24 days? #205706
Replies: 3 comments 1 reply
|
Ok!, 24 days is well beyond the stated "up to 3 working days" window, so this is worth flagging directly rather than assuming it's just a busy queue, that SLA is documented as the norm, not a best-case. A couple of practical notes:
When you file it, reference the specific advisory IDs/draft URLs and the exact request dates, that gives them something concrete to trace rather than a general "queue is slow" report, and mention the doc's 3-day claim directly since that's a fair ask for them to either honor or correct. |
|
I'm not sure where to look for pending action required. Here is all that I see: degenaro requested a CVE 3 weeks ago. I will file an issue with GitHub Support as you suggest. |
|
I met the same situation, I have been waiting for over a week, which is very slow for security responses. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Other
Discussion Details
Out project has draft security advisories for which CVEs were requested as long as 24 days ago. If it's no longer true that the "process may take up to 3 working days", can that be updated to reflect the time expected for review and assignment to be more accurate? Can you verify that we have 3 CVEs in queue for compliance-trestle? Thx.
All reactions