CVE-2026-12986

Unauthenticated administrative takeover via REST token exfiltration

Published Jun 24, 2026 · Updated Jun 24, 2026

SSRF in the Payara Server Admin GUI allows remote attackers to steal an administrator REST token through a crafted download URL. DownloadServlet accepts the user-controlled restUrl request parameter and passes it to ContentSource implementations instead of using the trusted session value. A logged-in administrator must follow the crafted request; the leaked gfresttoken can then be replayed for domain administration and WAR-based code execution.

CVSS severity7.3
High
EPSS probability0.27%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

SSRF in the Payara Server Admin GUI allows remote attackers to steal an administrator REST token through a crafted download URL. DownloadServlet accepts the user-controlled restUrl request parameter and passes it to ContentSource implementations instead of using the trusted session value. A logged-in administrator must follow the crafted request; the leaked gfresttoken can then be replayed for domain administration and WAR-based code execution.

The record

CVE
CVE-2026-12986
Published
Jun 24, 2026
Updated
Jun 24, 2026
Vendor
Payara
Product
Payara Server
Classifications
CWE-352, CWE-918, CAPEC-62, CAPEC-60, CAPEC-664, T1539
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 24, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 24, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.1.144 <4.1.2.191.56
  2. Affected versionversion=5.181 <=5.201.2
  3. Affected versionversion=5.20.0 <5.88.0
  4. Affected versionversion=5.2020.1 <=5.2022.5
  5. Affected versionversion=6.0.0 <6.39.0
  6. Affected versionversion=6.2023.1 <=6.2025.11
  7. Affected versionversion=7.0.0 <7.1.0
  8. Affected versionversion=7.2025.1 <7.2026.6

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Payara · Payara Serverversion=4.1.144 <4.1.2.191.56; version=5.181 <=5.201.2; version=5.20.0 <5.88.0; version=5.2020.1 <=5.2022.5; version=6.0.0 <6.39.0; version=6.2023.1 <=6.2025.11; version=7.0.0 <7.1.0; version=7.2025.1 <7.2026.6

Published CVSS scores

7.3GitHub Advisory DatabaseCVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-352Cross-Site Request Forgery (CSRF)
CWE-918Server-Side Request Forgery (SSRF)
CAPEC-62Cross Site Request Forgery
CAPEC-60Reusing Session IDs (aka Session Replay)
CAPEC-664Server Side Request Forgery
T1539Steal Web Session Cookie

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo