Apache Any23: Possible excessive allocation of resources reading input.

published 2023-07-05 3 y ago modified 2026-06-17 4 mo ago also GHSA-2gpr-j5vj-wvh2 , EUVD-2023-1925

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits: 0; none known

** UNSUPPORTED WHEN ASSIGNED ** Use of TikaEncodingDetector in Apache Any23 can cause excessive memory usage.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-34150 updated 2026-11-06 cvss 5.3

any23: possible excessive allocation of resources reading input

Red Hat Integration Camel K 1 any23 any23 Red Hat Integration Camel Quarkus 2 any23 any23
affected: no fix planned “Will not fix”
Red Hat build of Apache Camel for Spring Boot 3 any23 any23
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 2 y ago (2024-04-30)

Exploit prediction

1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
NVD	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
GitHub	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Affected packages

ecosystem	package	affected	fixed in
maven	org.apache.any23:apache-any23	<=2.7	no fix listed

Affected products

Apache Software Foundation Apache Any23

Classification

Weakness

CWE-20 Improper Input Validation
CWE-400 Uncontrolled Resource Consumption

References

lists.apache.org /thread/713tk23khbtbg940pb2ql8ggd4cvh6j1
vendor-advisory, web, mailing-list
nvd.nist.gov /vuln/detail/CVE-2023-34150
advisory
github.com /apache/any23
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary