Futureweb

Security

GlobalProtect accepted a cookie it did not integrity-check

Palo Alto says GlobalProtect can open a VPN session from a cookie it does not integrity-check. May's advisory is the fix. October 21 reporting says ransomware use started in June.

The short version

Palo Alto says CVE-2026-0257 is an authentication bypass because GlobalProtect relied on cookies without validation and integrity checking, which can open an unauthorized VPN session. The advisory is dated May 13, 2026. Panorama and Cloud NGFW are not affected.

A May flaw, a June campaign, an October headline

Palo Alto's advisory for CVE-2026-0257 is dated May 13, 2026, and the page records an update on June 3. The weakness is CWE-565: reliance on cookies without validation and integrity checking. The impact is an authentication bypass on the GlobalProtect portal and gateway that lets a remote, unauthenticated attacker establish a VPN connection. Severity is 7.8, high, and the listed urgency is highest. Palo Alto says it became aware of limited exploit attempts against unpatched devices that did not have mitigations. Help Net Security's October 21 article is the day's news: ransomware groups have been using the flaw since June. The advisory and Unit 42's threat brief are Palo Alto's own record. Help Net is the other account.The advisory is the story.

The exposure condition is a configuration

The advisory says Panorama and Cloud NGFW are not affected. Exposure requires a GlobalProtect portal or gateway with authentication-override cookies enabled, plus a specific certificate configuration the advisory describes. The fixed trains are listed on that page, by PAN-OS branch, and Prisma Access customers are on Palo Alto's own upgrade schedule. This brief does not copy the branch-by-branch matrix or the management-interface clicks an administrator uses to see whether the cookie options are on. Those steps are the vendor's checklist. The fact the paper needs is the condition: an override cookie that is accepted without an integrity check.What a CVE identifier is.

What the October reporting is allowed to add

Help Net says Unit 42 has been investigating intrusions linked to the vulnerability since early June, and that the October 19 update to the threat brief names ransomware operators using it for initial access. Unit 42's brief is the document the advisory itself tells readers to open for the latest information. The reporting describes attackers who then moved inside networks they had reached. This page keeps the initial-access fact and leaves the later movement in the threat brief. A second vulnerability chained after the VPN session is a different identifier. The cookie check is the one CVE-2026-0257 names.What an advisory must name.

Memory safety does not sign a cookie

A Rust rewrite of a portal would still be vulnerable if it treated an unsigned cookie as a session. The borrow checker does not compute a message authentication code, and it does not refuse a credential the programmer decided to trust. CVE-2026-0257 is a missing check, discovered inside PAN-OS, not a heap overflow in a parser. Remade with Rust removes lifetime bugs in the primitives it rebuilds. It does not reach into GlobalProtect and add the integrity check the May advisory describes. Claiming otherwise would hide the actual remedy, which is the fixed train on the firewall an operator still runs.What a CVSS score does not say.

The check is the product decision

The house rule that does match this flaw is older than the language choice. A grant is trusted because a key signed it, and the verifier checks that signature before the caller is anyone. Audience, purpose, and issuer have to be inside the signed bytes, so a token minted for one service is not a session on another. A cookie that skips integrity checking fails that rule even if every line around it is memory-safe. Futureweb's session brief is the same boundary in plainer words: a session cannot be a blob the server accepts because it arrived. GlobalProtect's override cookie, as Palo Alto describes it, was that blob.What a session cannot be.

Ransomware used the hole that was left

Help Net's account is that the groups used the bypass to get a foothold and, from there, a VPN session that also got past multifactor checks tied to the portal. That sentence is impact. It is not a map of the tools used afterward. The SafePay advisory filed beside this one is the day's ransomware document, and it names stolen credentials and edge devices in general. It is not a second writeup of CVE-2026-0257. Palo Alto's fix remains the May release train. October 21 did not produce a new patch. It produced a newsroom confirmation that the unpatched devices were still being used.The SafePay advisory counts the victims.

A MATA grant is a signature, not an override cookie

MATA's published model keeps the key on the holder's device. A caller proves that key, and the verifier checks the signature before the operation runs. There is no GlobalProtect portal in that handshake, and there is no authentication-override cookie whose integrity is optional. An unauthorized VPN session is the impact Palo Alto named. The mesh does not offer that session. The digital-freedom note is the public statement: encryption on the device, memory-safe code, and no requirement to leave the credential on an external server that might accept a cookie in its place. Operators who still publish a GlobalProtect gateway apply the advisory on that gateway.How MATA keeps keys on the device.

The holder checks, the portal does not substitute

The key stays with the holder, which is the brief already filed on the privacy desk. A device dropped from the roster stops verifying, because the signature no longer resolves to an enrolled key. That revocation is not available to a cookie the portal accepted without a check: the cookie's problem is that nothing strong was verified in the first place. A MATA call that fails verification fails closed, as an unknown caller, rather than as a VPN session with the attacker's chosen account. The certificate configuration Palo Alto mentions is a condition of exposure on PAN-OS. It is not the eMudhra compromise filed this morning, and the two documents should not be read as one incident.The key stays with the holder.

Patch the firewall that still terminates the VPN

The mesh boundary does not uninstall a PAN-OS firewall in front of a company network. If that firewall runs a GlobalProtect portal or gateway with override cookies enabled, the May advisory is the work: the fixed train listed for the branch, or the mitigation Palo Alto prints for devices that cannot move yet. Unit 42's brief is where Palo Alto is tracking exploitation. Help Net is the October 21 confirmation that ransomware crews did not wait. A MATA node behind a patched gateway is the ordinary case. A MATA node behind an unpatched GlobalProtect portal is still behind the bug the advisory describes, until that portal changes.A key the holder checks.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. Palo Alto advisory
  2. Unit 42 threat brief
  3. Help Net Security

Questions

When was CVE-2026-0257 published?

Palo Alto published the advisory on May 13, 2026 and updated it June 3. The weakness is CWE-565, reliance on cookies without validation and integrity checking. Severity on the advisory is 7.8, high, and the urgency is listed as highest.

Who does the advisory say is exposed?

Firewalls with a GlobalProtect portal or gateway when authentication-override cookies are enabled and a specific certificate configuration is present. Panorama and Cloud NGFW are not impacted. The advisory lists the fixed PAN-OS trains.

What did October 21 reporting add?

Help Net Security reported that ransomware groups have used the flaw since June, and that Unit 42 has investigated related intrusions since early June. Palo Alto's own advisory had already said it was aware of limited exploit attempts.

Does Rust add the missing integrity check?

No. A memory-safe program can still trust a cookie it never verifies. The check is a signature over the cookie, or a refusal to treat the cookie as a session. The language does not insert that check for you.

Does MATA open a VPN session from that cookie?

No. A MATA caller proves a key that stays on the device, and the verifier checks the signature before the call counts. An operator who still terminates GlobalProtect applies Palo Alto's May fix on that firewall.