Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-12986

Cross-Site Request Forgery (CSRF) in fish.payara.distributions:payara (CVE-2026-12986)

Summary

Vulnerability in fish.payara.distributions:payara (CVE-2026-12986). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 7.2026.6 or later.

Original description

The description as published by the source.

A critical vulnerability in Admin GUI in Payara Server Full 4.x, 5.x, 6.x, 7.x, 7.2026.x, 6.2025.x, 6.2024.x on All platforms that allows the attacker to leak the admin gfresttoken to an attacker-controlled host that can result in a full unauthenticated takeover of Payara admin domain.

A Server-Side Request Forgery (SSRF) vulnerability in the DownloadServlet of the Admin GUI in Payara Server allows a remote attacker to exfiltrate the administrator's REST session token (gfresttoken) to an attacker-controlled host via a crafted request URL. Combined with the absence of CSRF protection on DownloadServlet, an unauthenticated attacker can trick a logged-in administrator into triggering the token leak, then replay the stolen token to gain full administrative access to the Payara domain, leading to arbitrary code execution via WAR deployment. The vulnerability exists in the DownloadServlet and associated ContentSource implementations (LogViewerContentSource, LogFilesContentSource, LBConfigContentSource, ClientStubsContentSource) within the admingui:console-common module.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-12986 has been found in fish.payara.distributions:payara.
Risk of unauthorized operations or information disclosure.
What to do: upgrade fish.payara.distributions:payara to 7.2026.6 or later.
If unsure, ask your IT team or search "fish.payara.distributions:payara CVE-2026-12986" on the vendor's site.

CVE-2026-12986 (fish.payara.distributions:payara) — CWE-352
Patched: 7.2026.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

CSRF (CWE-352) exists in fish.payara.distributions:payara.

📍 Affected scope

Check the vendor advisory for the affected versions of fish.payara.distributions:payara.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7.2026.6.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで fish.payara.distributions:payara を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade fish.payara.distributions:payara to 7.2026.6

    ステージング環境で 7.2026.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven fish.payara.distributions:payara
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2026.6"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details