189 wires and counting

$ follow Google

Keep up with Google in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-05-11
stories 4

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

JAX HARDENS DESERIALIZATION TRUST MODEL AFTER SECURITY ADVISORY

By RepoJournal · Filed · About Google · Composed from the cited sources · methodology

JAX is documenting a critical trust boundary in its export deserialization path after identifying potential security risks in untrusted blob handling.

The JAX team issued a security advisory [1] flagging that `jax.export.deserialize` was accepting untrusted serialized objects without sufficient safeguards, prompting immediate documentation hardening. A new admonition in the export docs [1] now explicitly warns developers that deserialization expects trusted input only—closing the gap between API capability and safe usage. In parallel, the team shipped a structural fix [2] that uses abstract value information during deserialization to ensure py_tree objects maintain consistent shapes and dtypes throughout unflattening, rather than defaulting to placeholder floats. This prevents shape mismatches that could silently introduce bugs in downstream computations. The XLA dependency was also bumped [3] to pull in upstream fixes that likely complement these changes. Together, these moves harden JAX's serialization layer without breaking existing workflows.

Action items

References

  1. [1] PR #37441: docs(export): note deserialize trust boundary google/jax ↗
  2. [2] Using avals for deserialization of the py_tree. ↗ google/jax
  3. [3] Update XLA dependency to use revision http://github.com/openxla/xla/commit/59031c7d1c120837166ad812f64b4e4bbf05b7b6 google/jax ↗

Quick answers

What shipped in Google on May 11, 2026?
JAX is documenting a critical trust boundary in its export deserialization path after identifying potential security risks in untrusted blob handling. In total, 3 commits and 1 pull requests landed.
Who contributed to Google on May 11, 2026?
1 developer shipped this update, including copybara-service[bot].
What were the notable Google updates?
PR #37441: docs(export): note deserialize trust boundary, Using avals for deserialization of the py_tree, and Update XLA dependency to use revision http://github.com/openxla/xla/commit/59031c7d1c120837166ad812f64b4e4bbf05b7b6.