Add the missing withdrawal reply to the CVE-2024-7036 timeline

The CNA replied on 2026-08-12 like it did on the other eight records; the page was written from the record state alone because that reply was not to hand at the time. Its timeline now matches the rest of the batch.
This commit is contained in:
Classic298
2026-08-14 19:02:33 +02:00
parent 149090b480
commit e7f9628e61
@@ -35,7 +35,8 @@ This CVE was **withdrawn by its issuing CNA** after the dispute was escalated to
| 2026-08-03 | Open WebUI follows up with huntr / Protect AI. No response is received and the record is unchanged. |
| 2026-08-08 | With no response from huntr / Protect AI, Open WebUI escalates this record to the CVE Program Root. |
| 2026-08-12 | The CVE Program opens a formal dispute with huntr / Protect AI under CVE Program Rule 4.1 (Vulnerability Determination) and requests the CNA's response. |
| 2026-08-13 | <span className="badge badge--success cve-rejected">Officially rejected</span> huntr / Protect AI withdraws the record and it is updated on cve.org. **The CVE record is now officially REJECTED.** |
| 2026-08-12 | huntr / Protect AI replies to the CVE Program and agrees to withdraw the record. |
| 2026-08-13 | <span className="badge badge--success cve-rejected">Officially rejected</span> The record is updated on cve.org. **The CVE record is now officially REJECTED.** |
The record is now in the **REJECTED** state on cve.org, and that state propagates to NVD and downstream feeds. No action is required from users, and the CVE should not be treated as an Open WebUI vulnerability.