Vulnerability in Okta Access Gateway (CVE-2026-78552)
Summary
Vulnerability in Okta Access Gateway (CVE-2026-78552). Data can be tampered with by attackers.
Original description
The description as published by the source.
The Okta Access Gateway does not apply its Lua directive restriction to the application-level custom configuration field. The field is interpolated directly into the nginx server block without inspection, resulting in execution of injected directives.
Source: NIST National Vulnerability Database 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-78552 has been found in Okta Access Gateway.
Data can be tampered with by attackers. CVSS score: 6.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Okta Access Gateway CVE-2026-78552" on the vendor's site.
CVE-2026-78552 (Okta Access Gateway) — CWE-693 / CVSS v3 6.0
Attack vector: remote (network-reachable) / no user interaction
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.
A vulnerability (CWE-693) exists in Okta Access Gateway.
Check the vendor advisory for the affected versions of Okta Access Gateway.
Severity: Medium (CVSS 6.0/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Okta Access Gateway を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web trust.okta.com
- web nvd.nist.gov
- web github.com