The changes in this update
Valve brought the Boulder and Poseidon maps up to their latest Community Workshop versions. This is a map-content update; the announcement does not detail changed areas, gameplay systems, or modes.
The patch also fixes a case where a player could move too quickly while pressed against a wall. That wording points to one movement bug, not a stated overhaul of Counter-Strike 2 movement physics. The original wording is available in the Steam announcement.
What it means for cheat software
There is no mention of VAC, anti-cheat changes, account bans, detection waves, or new anti-cheat checks. As a result, this announcement does not support a claim that cheats were detected, nor does it prove that every product needs an urgent update.
It also includes no information about client memory layouts, interfaces, or network protocol changes. A CS2 patch alone cannot confirm whether a particular product is working or not. Check the current status with the product developer before purchasing, renewing, or launching. The cheat selection checklist explains why status, update history, and support matter more than a feature count.
Movement macro users should take notice
The only gameplay-facing fix is related to speed near walls. If your movement automation relied on that old behavior, its output around obstacles may now be different. Nothing in the notes confirms a required update for NovaMacro or Macros, but neither page should be treated as a guarantee that wall-adjacent movement will behave exactly as it did before.
The update does not establish that macros are more or less detectable. Valve made no such statement. Avoid trying to compensate for the corrected game behavior with settings that create unnatural inputs. For context on the role of updates, player behavior, and reports in detections, see why cheats get detected.
Launch now or wait?
This announcement contains no anti-cheat-related signal that justifies a blanket wait recommendation for all CS2 software. It is not a clean bill of health either: third-party software in online matches always carries account risk.
If your use case specifically depends on wall movement, wait for a confirmed status update from the product developer or verify the changed behavior outside competitive play. If it does not, the published notes alone do not provide a reason to change your launch decision. The safe launch checklist covers general precautions before starting the game.
Original source developer announcement