Skip to main content

SLE API for Java EUVDEUVD-2026-99227

| CVE-2026-54086 MEDIUM
Allocation of Resources Without Limits or Throttling (CWE-770)
2026-10-13 GitHub_M
5.3
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Connect to SLE listening service
  2. Delivery
    Send ISP1 PDU with oversized body-length field
  3. Exploit
    Server allocates unbounded byte array / stalls on truncated read
  4. Execution
    Memory exhaustion and unhandled exceptions
  5. Impact
    Service denial of availability

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource allocation limits
MITRE ATT&CK

1 technique across 1 tactic: Impact

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network connectivity to the SLE listening service and the ability to send an ISP1 TML/PDU message in which the attacker controls the 4-byte big-endian body-length field decoded in EE_APIPX_PDUMessageFactory. No authentication is required (PR:N) and the flaw affects default handling of the ISP1 PDU path in versions prior to 5.1.7 - no non-default feature toggle is named in the description, so standard configurations are vulnerable. The practical limiting factor is reachability: SLE services are normally exposed only within space-agency ground-station operational networks, not the public internet, which substantially narrows the realistic attacker set despite the unauthenticated network vector.

Impact

This is a genuine but moderate-priority availability issue, not a critical one. The CVSS 3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) is consistent with the description: a remote, unauthenticated, low-complexity attack that yields only limited availability impact (C:N/I:N/A:L) - no code execution, no data exposure. The vector and the description agree, which is a positive confidence signal. No EPSS score was provided in the input, so exploitation probability cannot be quantified; this absence is a data gap, not evidence of low likelihood. The CVE is NOT on the CISA KEV list and no public POC is referenced, so there is no confirmed or claimed active exploitation. The fix (commit 265118d, release 5.1.7) is confirmed and the root cause is clearly documented in source-code evidence (unbounded byte-array allocation from an attacker-controlled 4-byte length field, plus unterminated reads). The practical risk is dampened by the deployment context: SLE (Space Link Extension) is specialized space-ground-station software, so the realistic attacker population is small and the listening service is typically on controlled/isolated operational networks rather than the open internet. Net: a real, easily-triggered DoS worth patching on exposed SLE endpoints, but not a widespread-internet emergency.

Exploit ScenarioDerived

An attacker with network reach to the SLE listening service opens a connection and sends a malformed ISP1 PDU whose 4-byte body-length header declares an enormous size. The server decodes that length and attempts to allocate a correspondingly huge byte array (or blocks/leaks on a truncated read), causing memory exhaustion, unhandled exceptions, and denial of service. No authentication, user interaction, or special privileges are required, though no public exploit code is currently identified.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Denial of service in ESA's SLE API for Java (all versions prior to 5.1.7) allows an unauthenticated remote client of the SLE listening service to crash or degrade the service by sending a crafted ISP1 TML/PDU message whose 4-byte big-endian body-length field drives an unbounded byte-array allocation. Because the CVSS vector is PR:N/UI:N and no non-default feature toggle is required, any network-reachable instance in a standard configuration is exposed; however, the practical attacker set is narrowed by the fact that SLE endpoints are typically confined to space-agency ground-segment operational networks rather than the public internet. The flaw is fixed in 5.1.7, and no public exploit code was identified at time of analysis.

RemediationAI

Upgrade to the vendor-released patch, SLE API for Java 5.1.7, which is available from https://github.com/esa/sleapi-j/releases/tag/5.1.7 and corresponds to upstream commit 265118dfb70d1d0d991b085dcde4028c60bce4fc; the fix enforces a 10 MB cap on decoded ISP1 PDU body length, rejects negative or oversized lengths with SLE_E_INVALIDPDU, and converts silently-truncated reads into explicit exceptions. Because the fix is a source-level change to esa.sle.java.api.core, any application that embeds the library - including third-party SLE user or provider implementations - must be rebuilt against 5.1.7 rather than relying on a single runtime update. If immediate upgrade is not possible, the most effective compensating control is reachability reduction: restrict the SLE listening port at the firewall or VPN layer to known ground-segment peers, since the exploit path requires only the ability to open a TCP connection and send a TML header, and this control has the side effect of blocking legitimate remote partners until allow-lists are maintained. Operators can also cap the blast radius by setting a modest JVM maximum heap (-Xmx) so an unbounded allocation fails fast with OutOfMemoryError instead of exhausting host memory, though this trades degraded service capacity for containment and may cause unrelated allocation failures. Additional detection value comes from alerting on SleApiException, SLE_E_INVALIDPDU, EE_E_NOTCTX, and OutOfMemoryError events on SLE endpoints, and from ingress filtering of TML messages whose header declares a body length far above the legitimate maximum message size; none of these measures remove the root cause and should be treated only as interim mitigations until the 5.1.7 upgrade is applied.

Affected VersionsENISA

sleapi-j < 5.1.7

Affected Packages

euvd sleapi_j fix: 5.1.7

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

SLE API for Java is the European Space Agency's Java implementation of the CCSDS Space Link Extension (SLE) services, used to move telemetry and telecommand data between ground stations and control centres. Incoming SLE traffic is framed at the transport-mapping layer (TML): the first eight bytes of a TML message carry a header in which bytes 4-7 are an unsigned, big-endian 32-bit body length. In EE_APIPX_PDUMessageFactory that length was decoded and narrowed to a Java int and then used directly to size a byte[] read from the stream, with no upper bound - the classic CWE-770 pattern of allocating resources without limits or throttling, so a single small request can request an arbitrarily large allocation. The same decoding code also handled truncated or malformed input by returning null rather than signalling an error, allowing reads to terminate unexpectedly and leaving exceptions, partial reads, and resource leakage in the connection-handling path. The upstream fix bounds the PDU body length at 10 MB (MAX_PDU_BODY_LENGTH), validates the decoded value is non-negative and within range, and replaces the silent null return with an SleApiException (SLE_E_INVALIDPDU); a companion change in EE_APIPX_CtxMessageFactory rewrites the context-message read as a loop that keeps reading until the full declared body length is consumed and throws EE_E_NOTCTX on premature end of stream. Impact is limited to availability (C:N/I:N/A:L) with no confidentiality or integrity effect.

Know when Java gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
vuln.today AI 5.3 MEDIUM

Remote unauthenticated attacker sends a crafted PDU with no user interaction (AV:N/AC:L/PR:N/UI:N); impact is confined to availability via resource exhaustion with no confidentiality or integrity effect (C:N/I:N/A:L).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

Lifecycle Timeline

1
Patch available
Oct 13, 2026 - 20:20 EUVD

DescriptionCVE.org

SLE API for Java is an implementation of CCSDS Space Link Extension Services. Prior to 5.1.7, the ISP1 PDU handling path decodes an attacker-controlled body length and allocates a byte array without an upper bound, while malformed or truncated input can also terminate reads unexpectedly, allowing an unauthenticated client of the SLE listening service to trigger exceptions, resource leakage, and denial of service. This issue is fixed in version 5.1.7.

Threat Intelligence Overview

EPSS Score
0.5%
Top 60% exploitable
Prevalence
Low
ESA space-link-extension software, space-industry-specific ground-station deployments only
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact· derived
Medium

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

More in Java

View all
CVE-2012-4681 CRITICAL POC
9.8 Aug 28

Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m

CVE-2015-7450 CRITICAL POC
9.8 Jan 02

Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti

CVE-2013-2465 CRITICAL POC
9.8 Jun 18

Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent

CVE-2011-3544 CRITICAL POC
9.8 Oct 19

Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug

CVE-2010-1871 HIGH POC
8.8 Aug 05

JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to

CVE-2012-1723 CRITICAL POC
9.8 Jun 16

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up

CVE-2013-0422 CRITICAL POC
9.8 Jan 10

Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using

CVE-2012-0507 CRITICAL POC
9.8 Jun 07

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up

CVE-2015-4852 CRITICAL POC
9.8 Nov 18

The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers

CVE-2012-5076 CRITICAL POC
9.8 Oct 16

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow

CVE-2017-3066 CRITICAL POC
9.8 Apr 27

Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla

CVE-2012-0391 CRITICAL POC
9.8 Jan 08

The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy