Fedora Account System
Red Hat Associate
Red Hat Customer
NumberInput.looksLikeValidNumber() in FasterXML jackson-core pre-validates "stringified numbers" with two regular expressions: PATTERN_FLOAT ([+-]?[0-9]*[\.]?[0-9]+([eE][+-]?[0-9]+)?), present since 2.17.0, and PATTERN_FLOAT_TRAILING_DOT, added in 2.17.2. PATTERN_FLOAT places adjacent quantifiers over the same character class -- an optional [0-9]* run, an optional dot, then a required [0-9]+ run -- so input that ultimately fails to match forces Java's backtracking engine to retry every possible split point of the digit run. Matching cost therefore grows with the square of the input length. An attacker who can supply JSON that an application deserializes into a numeric target type reaches this method through jackson-databind's default String-to-number coercion (StdDeserializer and NumberDeserializers for BigDecimal, BigInteger, Double and Float). Because StreamReadConstraints.maxStringLength defaults to 20,000,000 characters, no constraint bounds the input before it reaches the regex. Testing by the reporter confirmed O(n^2) growth across five consecutive input-size doublings, with a single 160,000-character string consuming roughly 74 seconds in one call; a small number of concurrent requests of ordinary body size can therefore exhaust a server's request-handling thread pool. The affected method does not exist before 2.17.0, so 2.16.x and earlier releases are not affected. The fix replaces both regular expressions with a hand-rolled single-pass scan.
This issue has been addressed in the following products: Red Hat Build of Apache Camel 4.18 for Quarkus 3.33 Via RHSA-2026:83670 https://access.redhat.com/errata/RHSA-2026:83670
This issue has been addressed in the following products: Streams for Apache Kafka 3.2.2 Via RHSA-2026:86676 https://access.redhat.com/errata/RHSA-2026:86676
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:86706 https://access.redhat.com/errata/RHSA-2026:86706
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:92408 https://access.redhat.com/errata/RHSA-2026:92408
This issue has been addressed in the following products: Red Hat Satellite 6.18 for RHEL 9 Via RHSA-2026:92860 https://access.redhat.com/errata/RHSA-2026:92860
This issue has been addressed in the following products: Red Hat Satellite 6.16 for RHEL 8 Red Hat Satellite 6.16 for RHEL 9 Via RHSA-2026:92858 https://access.redhat.com/errata/RHSA-2026:92858
This issue has been addressed in the following products: Red Hat Satellite 6.17 for RHEL 9 Via RHSA-2026:92859 https://access.redhat.com/errata/RHSA-2026:92859
This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:95466 https://access.redhat.com/errata/RHSA-2026:95466
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:98606 https://access.redhat.com/errata/RHSA-2026:98606
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:98493 https://access.redhat.com/errata/RHSA-2026:98493
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 8.1 Via RHSA-2026:99017 https://access.redhat.com/errata/RHSA-2026:99017
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 9 Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 8 Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 10 Via RHSA-2026:99018 https://access.redhat.com/errata/RHSA-2026:99018