https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2026-78631.htmlhttps://patchthecve.com/cve/CVE-2026-78631.htmlTue, 22 Sep 2026 20:02:04 +0000MEDIUM 5.3: The Okta Hyperdrive Agent writes the decoded SAML bearer assertion to a local application log file at the default log level on every successful MFA completion. This insertion of sensitive information into the log file makes a live authentication credential readable by any local user with access to thttps://patchthecve.com/cve/CVE-2026-78629.htmlhttps://patchthecve.com/cve/CVE-2026-78629.htmlTue, 22 Sep 2026 20:06:42 +0000MEDIUM 5.6: The Okta Hyperdrive agent plugin returns a success response without a signed SAML assertion when the organization's policy requires no MFA for a given user. The response contains only a bare boolean validation indicator with no cryptographic artifact, resulting in an unverifiable authentication verdhttps://patchthecve.com/cve/CVE-2026-78627.htmlhttps://patchthecve.com/cve/CVE-2026-78627.htmlTue, 22 Sep 2026 20:10:34 +0000HIGH 7.3: The Okta Hyperdrive Integration installer does not mask the OAuth client secret when passed as an MSI property. The credential is recorded in plaintext in the installer log, the Application Event Log, and the process command line, all of which are readable by an authenticated local user on the workshttps://patchthecve.com/cve/CVE-2026-78574.htmlhttps://patchthecve.com/cve/CVE-2026-78574.htmlWed, 23 Sep 2026 18:12:49 +0000HIGH 7.5: The Okta Hyperdrive Integration plugin resolves a required assembly using a registry path within the current user's hive without integrity verification. The referenced path is loaded via Assembly.LoadFrom without signature validation, resulting in an unverified assembly executing within the context