How severe is CVE-2023-45278?

CVE-2023-45278 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-45278?

CVE-2023-45278 affects the following packages: org.yamcs:yamcs (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-45278?

Update org.yamcs:yamcs to 5.8.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-45278 is resolved across your whole dependency graph.

How do I detect CVE-2023-45278 in my Maven dependencies?

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

How do I mitigate CVE-2023-45278 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-2023-45278 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-45278, 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-2023-45278?

CVE-2023-45278 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 79th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-45278?

CVE-2023-45278 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.

When was CVE-2023-45278 published, and has it been updated?

CVE-2023-45278 was published on October 19, 2023 and was last updated on October 28, 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

CRITICAL severity

CVE-2023-45278 — yamcs

CRITICAL

CVE-2023-45278 is a critical-severity (CVSS 9.1) Path Traversal vulnerability in org.yamcs:yamcs. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.yamcs:yamcs — see the affected versions and patch details below.

Yamcs API Directory Traversal vulnerability

Also known asGHSA-43fw-536j-w37j

Published

Oct 19, 2023

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk+0.25%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.yamcs:yamcs

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

Directory Traversal vulnerability in the storage functionality of the API in Yamcs 5.8.6 allows attackers to delete arbitrary files via crafted HTTP DELETE request.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.yamcs:yamcs`	all versions	5.8.7`org.yamcs:yamcs:5.8.7`

Affected Products

1 product · 1 configurations

Application

yamcsspaceapplications

1 version

5.8.6

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.

Directory Traversal vulnerability in the storage functionality of the AP…

linkedin.comNVDOct 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.yamcs:yamcs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.yamcs:yamcs to 5.8.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-45278 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.

Frequently Asked Questions

Directory Traversal vulnerability in the storage functionality of the API in Yamcs 5.8.6 allows attackers to delete arbitrary files via crafted HTTP DELETE request.

O3 Security · Impact-Aware SCA

Is CVE-2023-45278 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-22Path Traversal

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

yamcs

4.9/10

Code-Review6/10

Maintained10/10

Branch-Protection0/10

Assessed Oct 26, 2026

Timeline

Disclosed

Oct 19, 2023

First exploit

Oct 25, 2023

7 days after disclosure — rapid exploitation

Last updated

Oct 28, 2026

Identifiers

CVE-2023-45278

GHSA-43fw-536j-w37j

References

Advisorygithub.com · CVE 2023 45278.json Advisorynvd.nist.gov · CVE 2023 45278 Webgithub.com · yamcs 5.8.6...yamcs 5.8.7 Weblinkedin.com · yamcs vulnerability assessment visionspace technologies Packagegithub.com · yamcs

Related vulnerabilities

Also affects yamcs

This CVE is critical severity — higher than any of the other 3 CVEs affecting yamcs (highest there: high).

CVE-2023-45279CVE-2023-45280CVE-2023-45277

Same weakness: CWE-22

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

CVE-2026-62331GHSA-4xm8-rg9h-jhq2CVE-2026-9083CVE-2026-115908CVE-2026-118667Browse all CWE-22

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2023-45278 — yamcs

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

Frequently Asked Questions

Is CVE-2023-45278 in your dependencies?