Apache Tomcat up to 8.5.82/8.5.100/9.0.116/10.1.53/11.0.20 JsonAccessLogValve escape output

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 2.21- |
Summary
A vulnerability classified as problematic has been found in Apache Tomcat up to 8.5.82/8.5.100/9.0.116/10.1.53/11.0.20. This affects an unknown part of the component JsonAccessLogValve. This manipulation causes escape output. This vulnerability is tracked as CVE-2026-34483. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Apache Tomcat up to 8.5.82/8.5.100/9.0.116/10.1.53/11.0.20. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component JsonAccessLogValve. The manipulation with an unknown input leads to a escape output vulnerability. The CWE definition for the vulnerability is CWE-116. The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved. As an impact it is known to affect integrity. The summary by CVE is:
Improper Encoding or Escaping of Output vulnerability in the JsonAccessLogValve component of Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.20, from 10.1.0-M1 through 10.1.53, from 9.0.40 through 9.0.116. Users are recommended to upgrade to version 11.0.21, 10.1.54 or 9.0.117 , which fix the issue.
The weakness was disclosed by Bartlomiej Dmitruk. The advisory is shared at lists.apache.org. This vulnerability is known as CVE-2026-34483 since 03/30/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/09/2026).
Upgrading to version 9.0.117, 10.1.54 or 11.0.21 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 8.0
- 8.1
- 8.2
- 8.3
- 8.4
- 8.5.0
- 8.5.1
- 8.5.2
- 8.5.3
- 8.5.4
- 8.5.5
- 8.5.6
- 8.5.7
- 8.5.8
- 8.5.9
- 8.5.10
- 8.5.11
- 8.5.12
- 8.5.13
- 8.5.14
- 8.5.15
- 8.5.16
- 8.5.17
- 8.5.18
- 8.5.19
- 8.5.20
- 8.5.21
- 8.5.22
- 8.5.23
- 8.5.24
- 8.5.25
- 8.5.26
- 8.5.27
- 8.5.28
- 8.5.29
- 8.5.30
- 8.5.31
- 8.5.32
- 8.5.33
- 8.5.34
- 8.5.35
- 8.5.36
- 8.5.37
- 8.5.38
- 8.5.39
- 8.5.40
- 8.5.41
- 8.5.42
- 8.5.43
- 8.5.44
- 8.5.45
- 8.5.46
- 8.5.47
- 8.5.48
- 8.5.49
- 8.5.50
- 8.5.51
- 8.5.52
- 8.5.53
- 8.5.54
- 8.5.55
- 8.5.56
- 8.5.57
- 8.5.58
- 8.5.59
- 8.5.60
- 8.5.61
- 8.5.62
- 8.5.63
- 8.5.64
- 8.5.65
- 8.5.66
- 8.5.67
- 8.5.68
- 8.5.69
- 8.5.70
- 8.5.71
- 8.5.72
- 8.5.73
- 8.5.74
- 8.5.75
- 8.5.76
- 8.5.77
- 8.5.78
- 8.5.79
- 8.5.80
- 8.5.81
- 8.5.82
- 8.5.100
- 9.0.116
- 10.1.0
- 10.1.1
- 10.1.2
- 10.1.3
- 10.1.4
- 10.1.5
- 10.1.6
- 10.1.7
- 10.1.8
- 10.1.9
- 10.1.10
- 10.1.11
- 10.1.12
- 10.1.13
- 10.1.14
- 10.1.15
- 10.1.16
- 10.1.17
- 10.1.18
- 10.1.19
- 10.1.20
- 10.1.21
- 10.1.22
- 10.1.23
- 10.1.24
- 10.1.25
- 10.1.26
- 10.1.27
- 10.1.28
- 10.1.29
- 10.1.30
- 10.1.31
- 10.1.32
- 10.1.33
- 10.1.34
- 10.1.35
- 10.1.36
- 10.1.37
- 10.1.38
- 10.1.39
- 10.1.40
- 10.1.41
- 10.1.42
- 10.1.43
- 10.1.44
- 10.1.45
- 10.1.46
- 10.1.47
- 10.1.48
- 10.1.49
- 10.1.50
- 10.1.51
- 10.1.52
- 10.1.53
- 11.0.0
- 11.0.1
- 11.0.2
- 11.0.3
- 11.0.4
- 11.0.5
- 11.0.6
- 11.0.7
- 11.0.8
- 11.0.9
- 11.0.10
- 11.0.11
- 11.0.12
- 11.0.13
- 11.0.14
- 11.0.15
- 11.0.16
- 11.0.17
- 11.0.18
- 11.0.19
- 11.0.20
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Escape outputCWE: CWE-116 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Tomcat 9.0.117/10.1.54/11.0.21
Timeline
03/30/2026 CVE reserved04/09/2026 Advisory disclosed
04/09/2026 VulDB entry created
04/09/2026 VulDB entry last update
Sources
Vendor: apache.orgAdvisory: lists.apache.org
Researcher: Bartlomiej Dmitruk
Status: Confirmed
CVE: CVE-2026-34483 (🔒)
GCVE (CVE): GCVE-0-2026-34483
GCVE (VulDB): GCVE-100-356677
Entry
Created: 04/09/2026 22:11Changes: 04/09/2026 22:11 (56)
Complete: 🔍
Cache ID: 216:372:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.