> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/resources/resources-ja/porishtosekyuriti/sekyuriti.md).

# セキュリティ情報

## ![](https://1572574871-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FihTXzKlZmF6LYKahCQ1r%2Fuploads%2F4ZdPX2c3Eo63XFwnO0MR%2FSummary2-Small-Icon.svg?alt=media\&token=05e9f825-3e25-40ff-8fac-4016ebd7e81c) 概要

このページには、Flosum のセキュリティアドバイザリが新しい順に一覧表示されています。各アドバイザリでは、公表済みの脆弱性が Flosum 製品にどのような影響を与えるか、また必要な対応があれば何をすべきかを説明しています。重要度は、脆弱性について\
&#x20;[National Vulnerability Database](https://nvd.nist.gov/).

<table><thead><tr><th width="110">公開日</th><th width="195">アドバイザリ</th><th width="160">CVE</th><th width="120">重要度</th><th>ステータス</th></tr></thead><tbody><tr><td>2026-10-28</td><td><a data-mention href="https://docs.flosum.com/resources/resources-ja/porishtosekyuriti/sekyuriti/nodejs-niokeru-brotli-no-cve-2026-111497.md">Node.js における Brotli の脆弱性 (CVE-2026-111497)</a></td><td>CVE-2026-111497</td><td>重大（9.2）</td><td>修正対応中</td></tr><tr><td>2026-10-27</td><td><a data-mention href="https://docs.flosum.com/resources/resources-ja/porishtosekyuriti/sekyuriti/php2shell-no-cve-2026-109618-oyobi-cve-2026-109619.md">PHP2Shell の脆弱性 (CVE-2026-109618 および CVE-2026-109619)</a></td><td>CVE-2026-109618<br>CVE-2026-109619</td><td>重大（9.2）</td><td>影響なし</td></tr></tbody></table>

アドバイザリについてご質問がある場合は、Flosum サポートにケースを起票してください。


---

# 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://docs.flosum.com/resources/resources-ja/porishtosekyuriti/sekyuriti.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.
