Okta Access Gateway 2026.44.0 Updates PHP for Two RCE Flaws
Tech GuruQuick Answer
Okta says Access Gateway releases before 2026.44.0 include affected PHP builds for CVE-2026-109618 and CVE-2026-109619. Upgrade to 2026.44.0, validate configuration and exposure, and retain appliance and change evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory Access Gateway appliances, exact releases, PHP runtime, administrative and application exposure, configuration drift, owners, and maintenance windows. Match appliances to the version boundary and verify the actual gateway configuration; do not treat the default-configuration mitigation as proof that a customized deployment is unaffected. Upgrade through the supported Okta channel to Access Gateway 2026.44.0 or later, which includes PHP 8.3.36. Confirm the running appliance and PHP versions, verify intended exposure and configuration, test protected applications and failover, review relevant logs where warranted, and retain evidence.
Last verified: 2026-10-23 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Okta Access Gateway appliances |
|---|---|
| Advisory | Okta OAG PHP runtime advisory |
| CVEs | CVE-2026-109618, CVE-2026-109619 |
| Authoritative release date | 2026-10-22 |
| Authority revision date | 2026-10-22 |
| Affected versions | Okta Access Gateway releases before 2026.44.0 that include PHP 8.3.x before 8.3.36; Okta says the default gateway configuration mitigates known exploitation paths. |
| Fixed version | Okta Access Gateway 2026.44.0 with PHP 8.3.36 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Okta states that the default Access Gateway configuration mitigates known exploitation of these vulnerabilities, but does not state that its product has been maliciously exploited.; no exploitation claim is inferred. |
What Changed
Okta published product-specific guidance for two PHP runtime vulnerabilities and supplied Access Gateway 2026.44.0 with the fixed PHP 8.3.36 runtime.
What To Validate Now
- Inventory. Inventory Access Gateway appliances, exact releases, PHP runtime, administrative and application exposure, configuration drift, owners, and maintenance windows.
- Establish applicability. Match appliances to the version boundary and verify the actual gateway configuration; do not treat the default-configuration mitigation as proof that a customized deployment is unaffected.
- Remediate. Upgrade through the supported Okta channel to Access Gateway 2026.44.0 or later, which includes PHP 8.3.36.
- Validate. Confirm the running appliance and PHP versions, verify intended exposure and configuration, test protected applications and failover, review relevant logs where warranted, and retain evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Okta does not provide a product-specific CVSS score or textual severity. The configuration statement is a mitigation boundary, not a substitute for the fixed appliance release.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
