Skip to content

Parser, deserialization, and resource-boundary batch

Signal: GitHub Security Advisories REST fallback surfaced parser and deserialization advisories updated on 2026-05-06 for Nokogiri and Jackson Databind.

Advisories covered

Why this is durable

Parsers and serializers are program interpreters. CSS selectors, XSLT, JSON type metadata, and polymorphic binding can consume unbounded resources or instantiate attacker-influenced behavior unless type and resource budgets are explicit.

Immediate triage

  1. Upgrade Nokogiri and Jackson Databind dependencies, including transitive copies bundled by frameworks.
  2. Identify endpoints that accept HTML/XML/CSS selectors, XSLT, JSON with polymorphic typing, or user-controlled object type metadata.
  3. Disable Jackson default typing for untrusted input; use allowlisted subtypes and DTOs instead of binding directly to domain objects.
  4. Put parser operations behind CPU, memory, recursion, node-count, transform-count, and wall-clock limits.
  5. Review availability telemetry for regex backtracking spikes, XSLT transform memory growth, and unexpected deserialization classes.

Durable controls

  • Treat every parser feature as a budgeted interpreter: measure and enforce limits before content reaches business logic.
  • Keep untrusted data in data-only formats; do not deserialize into arbitrary runtime classes.
  • Centralize XML/XSLT/CSS/JSON parser configuration so unsafe defaults cannot be reintroduced per endpoint.
  • Add regression corpora for selector backtracking, large transforms, gadget type metadata, and deeply nested documents.