Version Affected: RADIUS Agent 26.01.08 and earlier
Overview
Is the SecureAuth RADIUS Agent affected by CVE-2026-114938, the Java vulnerability known as Java4Shell?
Answer
Yes, if the Java runtime included with the RADIUS Agent is an affected version. The SecureAuth RADIUS Agent installs and runs its own Java runtime. Known as Java4Shell, the Common Vulnerabilities and Exposures (CVE) entry CVE-2026-114938 is a memory corruption flaw in some versions of the Java runtime that can allow remote code execution.
SecureAuth's RADIUS engineering team has reviewed the RADIUS Agent and assessed its practical exposure to this vulnerability as low, but SecureAuth still recommends upgrading every affected RADIUS Agent.
To find out whether a RADIUS Agent is affected, open a Command Prompt on the RADIUS Agent server and run the following command. It uses the default installation folder, so change the path if the RADIUS Agent is installed elsewhere:
"C:\Program Files\SecureAuth Corporation\SecureAuth IdP RADIUS Agent\bin\serverJre\jre\bin\java.exe" -versionThe Java version appears on the first line of the output. The RADIUS Agent is affected if that version is 17.0.6 or later and earlier than 25.0.5.1.
Resolution
Upgrade the RADIUS Agent to 26.01.09 or later. This release includes a fixed Java runtime that resolves CVE-2026-114938. Download the installer from the SecureAuth Product Downloads page, where it is listed as RADIUS Server under Infrastructure Add-ons. After upgrading, run the command above again and confirm that the reported Java version is 25.0.5.1 or later.
How To: Upgrade the SecureAuth RADIUS Server describes how to back up the RADIUS configuration, download the latest installer and run the in-place upgrade.
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.
Comments
0 comments
Please sign in to leave a comment.