# Disable Attachment Processor from ElasticSearch

**URL:** <https://discuss.elastic.co/t/disable-attachment-processor-from-elasticsearch/361401>\
**Category:** Elasticsearch\
**Created:** [June 13, 2024, 12:00pm UTC](https://discuss.elastic.co/t/disable-attachment-processor-from-elasticsearch/361401 "2024-06-13T12:00:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![akula.vamshee](https://avatars.discourse-cdn.com/v4/letter/a/278dde/32.png) [@akula.vamshee](https://discuss.elastic.co/u/akula.vamshee)\
**Post date:** [June 13, 2024, 12:34pm UTC](https://discuss.elastic.co/t/disable-attachment-processor-from-elasticsearch/361401/3 "2024-06-13T12:34:08Z")

</div>

Do you mean the Elasticsearch Distribution?

This page says that if we cannot upgrade the ES, then disable attachment processor.

> [@Elasticsearch 8.11.1 Security Update (ESA-2024-05)](https://discuss.elastic.co/t/elasticsearch-8-11-1-security-update-esa-2024-05/356458):
>
> Elasticsearch Uncaught Exception (ESA-2024-05) An uncaught exception in Elasticsearch \>= 8.4.0 and \< 8.11.1 occurs when an encrypted PDF is passed to an [attachment processor](https://www.elastic.co/guide/en/elasticsearch/reference/current/attachment.html) through the REST API. The Elasticsearch ingest node that attempts to parse the PDF file will crash. This does not happen with password-protected PDF files or with unencrypted PDF files. Affected Versions: Affects versions \>= 8.4.0 and \< 8.11.1 Solutions and Mitigations: The issue is resolved in version 8.11.1. This req…

Can you provide more details how we can achieve this using the original details in my post?

Let me know if you need more information.

---

_[View the full topic](https://discuss.elastic.co/t/disable-attachment-processor-from-elasticsearch/361401)._