Add dispute timelines to the vendor-disposition pages

Adds a Timeline to every vendor-disposition page recording the full dispute chronology, and expands the three settled records (15603, 29446, 63391) with a resolved callout confirming the CNA has withdrawn the record.

Each timeline now names the actor at every step and makes the escalation count explicit: the initial 2026-05-04 dispute with the CVE Program went unanswered, a second dispute followed on 2026-06-15, and for the still-open records a third escalation to the CVE Program's Root under the CVE Record Dispute Policy (v2.0.0) on 2026-07-02. NVD is recorded as declining to adjudicate and directing the dispute to the CVE Program.

Also corrects the CISA-ADP attribution on 63391, the 29446 public-disclosure date (2025-03-01, now sourced) and its confidential-disclosure framing, removes internal GHSA advisory IDs, and aligns naming (huntr / Protect AI) and headings (Timeline) across all seven pages.

Author: Classic298

docs/security/vendor-dispositions/cve-2024-7040.mdx

@@ -10,10 +10,27 @@ title: "CVE-2024-7040"
 | **CVE ID** | [CVE-2024-7040](https://www.cve.org/CVERecord?id=CVE-2024-7040) |
 | **Vendor Disposition** | Rejected, out of scope |
 | **Published** | 2025-10-15 |
-| **Issuing CNA** | huntr.dev (from a [bounty report](https://huntr.com/bounties/bd182309-4aa4-4747-941e-bbc1741955c1)) |
+| **Issuing CNA** | huntr / Protect AI (from a [bounty report](https://huntr.com/bounties/bd182309-4aa4-4747-941e-bbc1741955c1)) |
 | **Claimed Severity** | Medium (CVSS 4.9, CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N) |
 
 
+---
+
+## Timeline
+
+This CVE is formally disputed. The dispute is open and being pursued through the CVE Program's process; the assessment below is Open WebUI's position in the meantime.
+
+| Date | Event |
+| :--- | :--- |
+| 2024 | The underlying report (affecting ≤ v0.1.125) is submitted through Open WebUI's security channel and closed as out of scope (cross-admin access). |
+| 2025-10-15 | huntr / Protect AI publishes the CVE. |
+| 2026-05-04 | Open WebUI files a formal dispute with the CVE Program. The dispute goes unanswered. |
+| 2026-06-15 | Open WebUI files another dispute with the CVE Program; the Secretariat directs it to the issuing CNA (huntr / Protect AI), which owns the record. |
+| 2026-06-17 | Open WebUI contacts huntr / Protect AI directly. No response. |
+| 2026-07-02 | With the CNA non-responsive, Open WebUI escalates the dispute a third time, to the CVE Program's Root / Top-Level Root under the CVE Record Dispute Policy (v2.0.0). |
+
+As of 2026-07-02 the dispute remains open and the CVE record has not been amended. This disposition stands as Open WebUI's official assessment.
+
 ---
 
 ## What the CVE Claims

docs/security/vendor-dispositions/cve-2025-15603.mdx

@@ -15,12 +15,19 @@ title: "CVE-2025-15603"
 
 ---
 
-## Resolution
+:::tip Resolved: this CVE is now rejected
+The issuing CNA has withdrawn the record, so the official CVE entry now carries the `REJECTED` state and NVD and downstream feeds inherit it. The public record now matches Open WebUI's vendor disposition below, confirming our assessment that this was not a genuine vulnerability. There is no advisory and no affected Open WebUI release.
+:::
+
+## Timeline
 
 | Date | Event |
 | :--- | :--- |
 | 2026-03-09 | CVE-2025-15603 published by VulDB, derived from a huntr.com bounty report. |
+| 2026-05-04 | Open WebUI files a formal dispute with the CVE Program. The dispute goes unanswered. |
 | 2026-05-05 | Open WebUI publishes this disposition, rejecting the report as not a security issue. |
+| 2026-06-15 | Open WebUI files another dispute with the CVE Program; the Secretariat directs it to the issuing CNA (VulDB), which owns the record. |
+| 2026-06-17 | Open WebUI contacts VulDB directly. |
 | 2026-06-18 | VulDB withdraws the candidate. The official CVE record state becomes `REJECTED`. |
 
 Our disposition rejected this report on 2026-05-05. The issuing CNA followed later: on 2026-06-18 VulDB formally withdrew the candidate, so the official [CVE record](https://www.cve.org/CVERecord?id=CVE-2025-15603) now carries the `REJECTED` state, which NVD and downstream feeds inherit. The public record now matches the position we had already taken, and there is no advisory or affected Open WebUI release. The CNA's published rejection reads:

docs/security/vendor-dispositions/cve-2025-29446.mdx

@@ -15,12 +15,19 @@ title: "CVE-2025-29446"
 
 ---
 
-## Resolution
+:::tip Resolved: this CVE is now rejected
+The issuing CNA has withdrawn the record, so the official CVE entry now carries the `REJECTED` state and NVD and downstream feeds inherit it. The public record now matches Open WebUI's vendor disposition below, confirming our assessment that this was not a genuine vulnerability. There is no advisory and no affected Open WebUI release.
+:::
+
+## Timeline
 
 | Date | Event |
 | :--- | :--- |
 | 2025-04-21 | CVE-2025-29446 published by MITRE, derived from a public disclosure. |
+| 2026-05-04 | Open WebUI files a formal dispute with the CVE Program. The dispute goes unanswered. |
 | 2026-05-05 | Open WebUI publishes this disposition, rejecting the report as not a vulnerability. |
+| 2026-06-13 | Open WebUI files a dispute with NVD; NVD declines to adjudicate and directs the dispute to the CVE Program. |
+| 2026-06-15 | Open WebUI files another dispute with the CVE Program; MITRE, as the issuing CNA, reaches out to the original researcher. |
 | 2026-06-29 | The issuing CNA withdraws the record. The official CVE record state becomes `REJECTED`. |
 
 Our disposition rejected this report on 2026-05-05. The issuing CNA followed later: on 2026-06-29 the record was formally withdrawn, so the official [CVE record](https://www.cve.org/CVERecord?id=CVE-2025-29446) now carries the `REJECTED` state, which NVD and downstream feeds inherit. The public record now matches the position we had already taken, and there is no advisory or affected Open WebUI release. The CNA's published rejection reads:
@@ -51,7 +58,9 @@ The same pattern (admin-authenticated outbound URL probe to verify a configured
 
 ### Disclosure Pathway
 
-No report corresponding to this CVE was filed through the project's official reporting channel ([GitHub Security Advisories](https://github.com/open-webui/open-webui/security)) prior to publication. The issue was instead publicly disclosed with a proof-of-concept on 2025-03-21, roughly a month before the CVE was published on 2025-04-21, and was never filed through that channel. Public disclosure of vulnerability details before an advisory is published is prohibited under our [Confidential Disclosure policy](/security/security-policy#confidential-disclosure), independently of whether the issue was ever reported to us.
+No report corresponding to this CVE was filed through the project's official reporting channel ([GitHub Security Advisories](https://github.com/open-webui/open-webui/security)). The issue was instead published publicly, with a proof-of-concept, on [2025-03-01](https://github.com/l1uyi/cve-list/blob/main/cve-list/open-webui-ssrf.md), roughly seven weeks before the CVE was assigned on 2025-04-21.
+
+Our [Confidential Disclosure policy](/security/security-policy#confidential-disclosure) asks reporters not to publish vulnerability details before a fix and advisory are available. This exists to protect users and deployments: releasing a working proof-of-concept before operators have a fix to apply opens a window in which live instances are exposed with no remedy available, which is precisely the harm coordinated disclosure is meant to prevent. A report that had already been published in full before reaching us would not be accepted through our process for that reason. This is a point about disclosure conduct, not about the validity of the CVE: this record is rejected on the substance above, an admin-only endpoint behaving as designed, and the disclosure pathway is noted only to record that the project's coordinated process was never engaged.
 
 ---
 

docs/security/vendor-dispositions/cve-2025-63391.mdx

@@ -10,17 +10,24 @@ title: "CVE-2025-63391"
 | **CVE ID** | [CVE-2025-63391](https://www.cve.org/CVERecord?id=CVE-2025-63391) |
 | **Vendor Disposition** | Rejected, mischaracterized |
 | **Published** | 2025-12-18 |
-| **Issuing CNA** | MITRE (CISA-ADP), from a [public disclosure](https://gist.github.com/Cristliu/13c41b97285b776275bc8bfd3504e51b) |
+| **Issuing CNA** | MITRE, from a [public disclosure](https://gist.github.com/Cristliu/13c41b97285b776275bc8bfd3504e51b) (CVSS enrichment contributed by CISA-ADP) |
 | **Claimed Severity** | High (CVSS 7.5, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) |
 
 ---
 
-## Resolution
+:::tip Resolved: this CVE is now rejected
+The issuing CNA has withdrawn the record, so the official CVE entry now carries the `REJECTED` state and NVD and downstream feeds inherit it. The public record now matches Open WebUI's vendor disposition below, confirming our assessment that this was not a genuine vulnerability. There is no advisory and no affected Open WebUI release.
+:::
+
+## Timeline
 
 | Date | Event |
 | :--- | :--- |
-| 2025-12-18 | CVE-2025-63391 published by MITRE (CISA-ADP), derived from a public disclosure. |
+| 2025-12-18 | CVE-2025-63391 published by MITRE, derived from a public disclosure (CVSS enrichment contributed by CISA-ADP). |
+| 2026-05-04 | Open WebUI files a formal dispute with the CVE Program. The dispute goes unanswered. |
 | 2026-05-05 | Open WebUI publishes this disposition, rejecting the report as mischaracterized. |
+| 2026-06-13 | Open WebUI files a dispute with NVD; NVD declines to adjudicate and directs the dispute to the CVE Program. |
+| 2026-06-15 | Open WebUI files another dispute with the CVE Program; MITRE, as the issuing CNA, reaches out to the original researcher. |
 | 2026-06-29 | The issuing CNA withdraws the record. The official CVE record state becomes `REJECTED`. |
 
 Our disposition rejected this report on 2026-05-05. The issuing CNA followed later: on 2026-06-29 the record was formally withdrawn, so the official [CVE record](https://www.cve.org/CVERecord?id=CVE-2025-63391) now carries the `REJECTED` state, which NVD and downstream feeds inherit. The public record now matches the position we had already taken, and there is no advisory or affected Open WebUI release. The CNA's published rejection reads:

docs/security/vendor-dispositions/cve-2026-0765.mdx

@@ -14,6 +14,22 @@ title: "CVE-2026-0765"
 | **Claimed Severity** | High (CVSS 8.8, CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) |
 
 
+---
+
+## Timeline
+
+This CVE is formally disputed. The dispute is open and being pursued through the CVE Program's process; the assessment below is Open WebUI's position in the meantime.
+
+| Date | Event |
+| :--- | :--- |
+| 2025-10 | ZDI submits the underlying report through Open WebUI's security channel; Open WebUI closes it as out of scope per its published security policy. |
+| 2026-01-23 | ZDI publishes the CVE (ZDI-26-031) despite the vendor's out-of-scope disposition. |
+| 2026-05-04 | Open WebUI files a formal dispute with the CVE Program and notifies ZDI directly. Neither responds. |
+| 2026-06-15 | Open WebUI files another dispute with the CVE Program; the Secretariat directs it to the issuing CNA (ZDI), which owns the record. The request is subsequently closed. |
+| 2026-07-02 | With the CNA non-responsive, Open WebUI escalates the dispute a third time, to the CVE Program's Root / Top-Level Root under the CVE Record Dispute Policy (v2.0.0). |
+
+As of 2026-07-02 the dispute remains open and the CVE record has not been amended. This disposition stands as Open WebUI's official assessment.
+
 ---
 
 ## What the CVE Claims

docs/security/vendor-dispositions/cve-2026-0766.mdx

@@ -14,6 +14,22 @@ title: "CVE-2026-0766"
 | **Claimed Severity** | High (CVSS 8.8, CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) |
 
 
+---
+
+## Timeline
+
+This CVE is formally disputed. The dispute is open and being pursued through the CVE Program's process; the assessment below is Open WebUI's position in the meantime.
+
+| Date | Event |
+| :--- | :--- |
+| 2025-10 | ZDI submits the underlying report through Open WebUI's security channel; Open WebUI closes it as out of scope per its published security policy. |
+| 2026-01-23 | ZDI publishes the CVE (ZDI-26-032) despite the vendor's out-of-scope disposition. |
+| 2026-05-04 | Open WebUI files a formal dispute with the CVE Program and notifies ZDI directly. Neither responds. |
+| 2026-06-15 | Open WebUI files another dispute with the CVE Program; the Secretariat directs it to the issuing CNA (ZDI), which owns the record. The request is subsequently closed. |
+| 2026-07-02 | With the CNA non-responsive, Open WebUI escalates the dispute a third time, to the CVE Program's Root / Top-Level Root under the CVE Record Dispute Policy (v2.0.0). |
+
+As of 2026-07-02 the dispute remains open and the CVE record has not been amended. This disposition stands as Open WebUI's official assessment.
+
 ---
 
 ## What the CVE Claims

docs/security/vendor-dispositions/cve-2026-0767.mdx

@@ -14,6 +14,22 @@ title: "CVE-2026-0767"
 | **Claimed Severity** | Medium (CVSS 5.3, CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) |
 
 
+---
+
+## Timeline
+
+This CVE is formally disputed. The dispute is open and being pursued through the CVE Program's process; the assessment below is Open WebUI's position in the meantime.
+
+| Date | Event |
+| :--- | :--- |
+| 2025-10 | ZDI submits the underlying report through Open WebUI's security channel; Open WebUI closes it as out of scope per its published security policy. |
+| 2026-01-23 | ZDI publishes the CVE (ZDI-26-033) despite the vendor's out-of-scope disposition. |
+| 2026-05-04 | Open WebUI files a formal dispute with the CVE Program and notifies ZDI directly. Neither responds. |
+| 2026-06-15 | Open WebUI files another dispute with the CVE Program; the Secretariat directs it to the issuing CNA (ZDI), which owns the record. The request is subsequently closed. |
+| 2026-07-02 | With the CNA non-responsive, Open WebUI escalates the dispute a third time, to the CVE Program's Root / Top-Level Root under the CVE Record Dispute Policy (v2.0.0). |
+
+As of 2026-07-02 the dispute remains open and the CVE record has not been amended. This disposition stands as Open WebUI's official assessment.
+
 ---
 
 ## What the CVE Claims
@@ -32,6 +48,8 @@ Open WebUI is a backend application that exposes an HTTP interface. Whether that
 
 The CVSS vector itself acknowledges the impracticality: AV:A (Adjacent Network) and AC:H (High Attack Complexity) reflect that the scenario requires both an unencrypted deployment *and* a network-adjacent attacker positioned to intercept traffic. In any conventional production deployment behind TLS termination, the scenario does not arise.
 
+The vector cited here is the one ZDI assigned in the record under dispute (CVSS 5.3, AC:H). NVD's enrichment later re-scored it to 6.5 with AC:L, but the determining condition is unchanged: the traffic is interceptable only if the operator runs Open WebUI over plain HTTP, which is a deployment choice, not an Open WebUI defect.
+
 ### Applicable Security Policy Rules
 
 - **[Rule 1](/security/security-policy#reporting-guidelines):** Expected protocol behavior is not a vulnerability. HTTP's cleartext property is the textbook example.