ZeroHour
Story · 1 source · 2 articlesfirst updated ()

Payara Server 7.2026.1.RC1: Arbitrary EJB Method Invocation via Insecure Reflection and OS Command Execution via SSI #exec Directive

highVulnerabilityimportance 35
What's new: Initial merged summary for this story (no previous summary existed). Consolidated two full-disclosure reports published 2026-09-04 covering two distinct issues in Payara Server 7.2026.1.RC1: arbitrary EJB method invocation via insecure reflection in HTTP EJB endpoints, and arbitrary OS command execution via SSI #exec directives. The two reports agree on the affected version and publication date…
Merged summary · glm-5.3-flash · rewritten as coverage arrives

Two same-day full disclosures (2026-09-04) affect Payara Server 7.2026.1.RC1: HTTP EJB endpoints allow arbitrary EJB method invocation through attacker-controlled reflection, dynamic class loading, unsafe deserialization, and arbitrary JNDI lookups without…

Two separate full-disclosure reports, both published on 2026-09-04, describe vulnerabilities in the same product and version: Payara Server 7.2026.1.RC1. The first describes HTTP-accessible EJB invocation mechanisms that depend on attacker-controlled reflection, dynamic class loading, and unsafe deserialization. Remote clients can perform arbitrary JNDI lookups, resolve attacker-supplied class names, and invoke EJB business methods without sufficient authorization enforcement or input restriction; both the deprecated InvokeEJBServlet and other endpoints are affected in version 7.2026.1.RC1. The second describes a flaw in Payara Server's Server-Side Includes (SSI) implementation: user-controlled SSI directives, specifically #exec, are passed directly to Runtime.exec() without validation, sanitization, or restriction. An attacker who can cause the server to process an SSI file such as .shtml can execute arbitrary operating system commands. Neither report provides a CVE identifier, and there are no factual disagreements between the two reports; they describe distinct issues affecting the same disclosed version.

  • Affected product and version (stated in both reports): Payara Server 7.2026.1.RC1
  • Disclosure type and date (both reports): Full Disclosure, published 2026-09-04 (timestamps 2026-09-04T00:13:07.000Z and 2026-09-04T00:13:09.000Z)
  • EJB issue: HTTP-accessible EJB invocation mechanisms rely on attacker-controlled reflection, dynamic class loading, and unsafe deserialization
  • EJB issue: Remote clients can perform arbitrary JNDI lookups, resolve attacker-supplied class names, and invoke EJB business methods without sufficient authorization enforcement or input restriction
  • EJB issue: Both the deprecated InvokeEJBServlet and other endpoints are affected in version 7.2026.1.RC1
  • SSI issue: User-controlled SSI #exec directives are passed directly to Runtime.exec() without validation, sanitization, or restriction
  • SSI issue: Affects processing of .shtml files on Payara Server 7.2026.1.RC1 and allows arbitrary operating system command execution
  • No CVE identifiers were provided in either report
VendorsPayara

Coverage timeline

  1. · 11d ago
    Full Disclosure· 33
    Payara 7.2026.1.RC1 Arbitrary EJB Method Invocation via Insecure Reflection in Payara Server

    Payara Server 7.2026.1.RC1 HTTP EJB endpoints rely on attacker-controlled reflection and JNDI lookups without authorization, enabling arbitrary EJB method invocation.

  2. · 11d ago
    Full Disclosure· 35
    Payara 7.2026.1.RC1 Remote Code Execution via Server-Side Includes #exec Directive in Payara Server

    Payara Server 7.2026.1.RC1 executes arbitrary OS commands when user-controlled Server-Side Includes #exec directives are passed to Runtime.exec without validation.