How severe is CVE-2021-21234?

CVE-2021-21234 has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-21234?

CVE-2021-21234 affects the following packages: eu.hinsch:spring-boot-actuator-logview (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-21234?

Update eu.hinsch:spring-boot-actuator-logview to 0.2.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21234 is resolved across your whole dependency graph.

How do I detect CVE-2021-21234 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for eu.hinsch:spring-boot-actuator-logview, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-21234 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2021-21234 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2021-21234, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-21234?

CVE-2021-21234 has an EPSS (Exploit Prediction Scoring System) score of 21.0%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2021-21234?

CVE-2021-21234 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2021-21234?

A Nuclei detection template exists for CVE-2021-21234, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2021-21234 published, and has it been updated?

CVE-2021-21234 was published on January 5, 2021 and was last updated on July 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2021-21234 — spring-boot-actuator-logv…

HIGHFix: lukashinsch/spring-boot-actuator-logview@1c76e1e

CVE-2021-21234 is a high-severity (CVSS 7.7) Path Traversal vulnerability in eu.hinsch:spring-boot-actuator-logview. 2 public exploit references exist, so weaponization risk is real. A fix is available for eu.hinsch:spring-boot-actuator-logview — see the affected versions and patch details below.

Directory Traversal in spring-boot-actuator-logview

Also known asGHSA-p4q6-qxjx-8jgp

Published

Jan 5, 2021

Updated

Jul 9, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

21.0%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-21234 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕eu.hinsch:spring-boot-actuator-logview

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

spring-boot-actuator-logview in a library that adds a simple logfile viewer as spring boot actuator endpoint. It is maven package "eu.hinsch:spring-boot-actuator-logview". In spring-boot-actuator-logview before version 0.2.13 there is a directory traversal vulnerability. The nature of this library is to expose a log file directory via admin (spring boot actuator) HTTP endpoints. Both the filename to view and a base folder (relative to the logging folder root) can be specified via request parameters. While the filename parameter was checked to prevent directory traversal exploits (so that filename=../somefile would not work), the base folder parameter was not sufficiently checked, so that filename=somefile&base=../ could access a file outside the logging base directory). The vulnerability has been patched in release 0.2.13. Any users of 0.2.12 should be able to update without any issues as there are no other changes in that release. There is no workaround to fix the vulnerability other than updating or removing the dependency. However, removing read access of the user the application is run with to any directory not required for running the application can limit the impact. Additionally, access to the logview endpoint can be limited by deploying the application behind a reverse proxy.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`eu.hinsch:spring-boot-actuator-logview`	all versions	0.2.13`eu.hinsch:spring-boot-actuator-logview:0.2.13`

Affected Products

1 product · 1 configurations

Application

spring-boot-actuator-logviewspring-boot-actuator-logview_project

≤ 0.2.12

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

spring-boot-actuator-logview in a library that adds a simple logfile vie…

github.comGithubOct 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for eu.hinsch:spring-boot-actuator-logview, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update eu.hinsch:spring-boot-actuator-logview to 0.2.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21234 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

How to detect CVE-2021-21234

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2021-21234 -u https://target

Template: Spring Boot Actuator Logview Directory Traversal
Severity: high
Impact: This vulnerability can lead to unauthorized access to sensitive information stored on the server.
Remediation: Apply the latest security patches or upgrade to a patched version of Spring Boot Actuator.

Template by ProjectDiscovery nuclei-templates (gy741, pikpikcu), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2021-21234 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.7/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

CWE Classification

Weaponization

Timeline

Disclosed

Jan 5, 2021

First exploit

Oct 19, 2021

Last updated

Jul 9, 2026

Identifiers

CVE-2021-21234

GHSA-p4q6-qxjx-8jgp

References

Advisorygithub.com Advisorysearch.maven.org Advisorynvd.nist.gov Fixgithub.com Fixgithub.com

Related vulnerabilities

This CVE is high severity; 6 of 8 other CVEs with CWE-22 are rated as high or higher (top: critical).

CVE-2026-63445CVE-2026-72697CVE-2026-74907CVE-2026-63225CVE-2026-86071CVE-2026-45140CVE-2026-72695CVE-2026-85731Browse all CWE-22

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 9, 2026

CVE-2021-21234 — spring-boot-actuator-logv…

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect CVE-2021-21234

Frequently Asked Questions

Is CVE-2021-21234 in your dependencies?