> For the complete documentation index, see [llms.txt](https://docs.pinot.apache.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pinot.apache.org/release-1.6.0/reference/release-notes/releases/1.5.1.md).

# 1.5.1

Release Notes for 1.5.1

Apache Pinot 1.5.1 is a **security patch release** based on 1.5.0. It contains only dependency updates and dependency-exclusion changes to resolve reported CVEs — **no functional, API, configuration, or wire-format changes**. A vulnerability scan of the 1.5.1 binary distribution reports **0 critical and 0 high** findings.

## Upgrade notes

Drop-in security update for 1.5.0 — no behavioral changes. Upgrade by replacing the 1.5.0 binary or Docker image with the 1.5.1 equivalent.

## Security fixes

| Dependency                           | 1.5.0 → 1.5.1                                      | CVEs addressed                                                                                                                 |
| ------------------------------------ | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Netty (`netty-bom`)                  | `4.1.122.Final` → `4.1.134.Final`                  | CVE-2025-55163, CVE-2025-59419, CVE-2026-33870, CVE-2026-33871, CVE-2026-42579, CVE-2026-42583, CVE-2026-42584, CVE-2026-42587 |
| Apache Log4j Core                    | `2.25.3` → `2.26.0`                                | CVE-2026-34478, CVE-2026-34479, CVE-2026-34480, CVE-2026-34481                                                                 |
| async-http-client                    | `3.0.7` → `3.0.10`                                 | CVE-2026-45300                                                                                                                 |
| Apache HttpClient 5                  | `5.6` → `5.6.1`                                    | CVE-2026-40542                                                                                                                 |
| Apache Pulsar (bundles BouncyCastle) | `4.0.9` → `4.0.10` (bcprov/bcpkix/bcutil → `1.84`) | CVE-2026-5598, CVE-2026-0636, CVE-2026-5588                                                                                    |
| commons-configuration2               | `2.13.0` → `2.15.0`                                | CVE-2026-45205                                                                                                                 |

## CVE-2026-2332 (Jetty request smuggling)

The only Jetty in Pinot's distribution was Hadoop's embedded `HttpServer2`, which Pinot never starts. As of 1.5.1 it is excluded from the Hadoop dependencies and stripped from the shaded jars ([#18659](https://github.com/apache/pinot/pull/18659)), so Jetty no longer ships in the distribution at all. Jetty 9.4.x itself is end-of-life with no available patch; removing the unused artifact is the resolution.

## Full changelog

[`release-1.5.0...release-1.5.1`](https://github.com/apache/pinot/compare/30fdfeea3a533d61d4eaf4c8050f5f4c07493de4...020ff0d0538b2079d4cf4cb2676a191c87c95d4d)


---

# 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.pinot.apache.org/release-1.6.0/reference/release-notes/releases/1.5.1.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.