Note the chaining exception on the LLM-output out-of-scope status

The short Status claims stated the risk is out of scope flatly. They now carry the same caveat the page body already spells out: it is out of scope on its own, but in scope when proven as part of a chain with a legitimate Open WebUI vulnerability per the Security Policy.

docs/security/accepted-risks/index.mdx

@@ -44,5 +44,5 @@ A residual whose practical impact is dominated by network and scheduling noise,
 
 | Risk | Class | Mitigation | Status |
 | :--- | :--- | :--- | :--- |
-| [LLM output unpredictability](./llm-output-unpredictability) | Inherent model behavior (OWASP LLM Top 10) | System hardened around the model; model bound by caller's privileges | Inherent to LLMs; out of scope as a vulnerability |
+| [LLM output unpredictability](./llm-output-unpredictability) | Inherent model behavior (OWASP LLM Top 10) | System hardened around the model; model bound by caller's privileges | Inherent to LLMs; out of scope on its own, unless chained with a legitimate vulnerability (see [Security Policy](../security-policy)) |
 | [Authentication timing side-channel](./auth-timing) | CWE-208, Observable Timing Discrepancy | bcrypt cost equalised across all sign-in paths | Mitigated, residual accepted |

docs/security/accepted-risks/llm-output-unpredictability.mdx

@@ -7,7 +7,7 @@ title: "LLM Output Unpredictability"
 |  |  |
 | :--- | :--- |
 | **Class** | Inherent model behavior (prompt injection, jailbreaks, unsafe or hallucinated output) — OWASP LLM Top 10 |
-| **Status** | Inherent to LLMs; not a remediable application defect; out of scope as a vulnerability |
+| **Status** | Inherent to LLMs; not a remediable application defect; out of scope as a vulnerability on its own, unless proven as part of a chain with a legitimate Open WebUI vulnerability per the [Security Policy](../security-policy) |
 
 ---