ZeroHour
Full Disclosurepublished ()ingested
Part of a story covered by 2 sources: “Payara Server 7.2026.1.RC1: Arbitrary EJB Method Invocation via Insecure Reflection and OS Command Execution via SSI #exec Directive” — merged summary and timeline →

Payara 7.2026.1.RC1 Arbitrary EJB Method Invocation via Insecure Reflection in Payara Server

highVulnerabilityimportance 33
AI summary · glm-5.3-flash

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

Payara Server exposes multiple 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.

  • Endpoints allow remote JNDI lookups and attacker-supplied class resolution
  • Relies on attacker-controlled reflection, dynamic class loading, and unsafe deserialization
  • Authorization enforcement and input restriction are insufficient, including in deprecated InvokeEJBServlet
VendorsPayara
Full article

Posted by Ron E on Sep 03 Payara Server exposes multiple HTTP-accessible EJB invocation mechanisms that rely on attacker-controlled reflection, dynamic class loading, and unsafe deserialization. These endpoints allow remote clients to perform arbitrary JNDI lookups, resolve attacker-supplied class names, and invoke EJB business methods via reflection without sufficient authorization enforcement or input restriction. Both the deprecated InvokeEJBServlet and the...

This source does not provide full text. Read it at seclists.org.