> For the complete documentation index, see [llms.txt](https://operations.clausebase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://operations.clausebase.com/security/security-log.md).

# Security Log

The following high-profile (or widely published) bugs were mitigated or deemed not relevant for ClauseBase:

* **6 December 2026** — [CVE-2025-55182](https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components) (ReactJS server components): ClauseBase does not make use of ReactJS server-side, so is not vulnerable.
* **21 July 2025** — [CVE-2025-53770](https://msrc.microsoft.com/blog/2025/07/customer-guidance-for-sharepoint-vulnerability-cve-2025-53770/) (Sharepoint): As this only affects on-premise installations of Sharepoint, ClauseBase is not vulnerable.
* **23 June 2025** — [CVE-2025-6019](https://security-tracker.debian.org/tracker/CVE-2025-6019) *(udisks vulnerability)*: This [widely published](https://www.bleepingcomputer.com/news/linux/new-linux-udisks-flaw-lets-attackers-get-root-on-major-linux-distros/) exploit requires the udisks daemon, which is primarily installed on desktop Linux systems for managing removable storage through GUI interfaces. Our Ubuntu servers don't run udisks as it's unnecessary for server operations. Additionally, the exploit requires local user access.
* **23 June 2025 —** [CVE-2025-6018](https://security-tracker.debian.org/tracker/CVE-2025-6018) *(PAM vulnerability)*: This [widely published](https://www.bleepingcomputer.com/news/linux/new-linux-udisks-flaw-lets-attackers-get-root-on-major-linux-distros/) vulnerability allows bypassing password prompts when chained with the udisks exploit, but also requires an existing local user session to trigger. Our servers have no local users, no physical access, and only allow authenticated SSH connections behind a firewall.
* **2 July 2024** — Affected (but mitigated through other measures, so probably not exploitable) by the ["regreSSHion" exploit in SSH](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-6387); patched all servers
* **9 June 2024** — ClauseBase is not affected by the 9.8 severity PHP-CGI issue (Windows only).
* **29 March 2024** — ClauseBase is [not affected](https://ubuntu.com/security/CVE-2024-3094) by the [xz Utils backdoor](https://arstechnica.com/security/2024/03/backdoor-found-in-widely-used-linux-utility-breaks-encrypted-ssh-connections/).
* **7 June 2023** — ClauseBase is not affected by the[ VMware Aria Operations for Networks exploit](https://www.cvedetails.com/cve/CVE-2023-20887/?q=CVE-2023-20887).
* **11 April 2023** — ClauseBase is not affected by the [Common Log File System vulnerability (Windows only)](https://www.cvedetails.com/cve/CVE-2023-28252/?q=CVE-2023-28252).
* **24 December 2022** — ClauseBase is not affected by the [SMB issue for Linux kernel 5.15](https://www.zdnet.com/article/patch-now-serious-linux-kernel-security-hole-uncovered/).
* **19 May 2022** — ClauseBase is not affected by VMWare security issue [CVE-2022-22960](https://kb.vmware.com/s/article/88099) or BIG-IP exploit [CVE-2022-1388](https://support.f5.com/csp/article/K23605346).
* **21st April 2022** — ClauseBase has been patched against the [cryptographic security issue CVE-2022-21449](https://www.oracle.com/security-alerts/cpuapr2022.html).
* **12 December 2021** — ClauseBase is not affected by the Log4J vulnerability [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://operations.clausebase.com/security/security-log.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.