{"id":"CVE-2026-126366","aliases":["AZL-114061","DHI-4lzs-kcmy-bnh7-x5g2","EUVD-2026-124750","GHSA-73v3-wf97-vpgj","UBUNTU-CVE-2026-126366"],"status":"published","title":"msgpack-java JRuby decoder allocates from declared header counts with no cap: 5-byte message forces multi-GiB OOM","description":"MessagePack for Ruby is an implementation of the MessagePack binary serialization format. Prior to 1.8.7, the Java-platform msgpack gem for JRuby allocated arrays and byte buffers directly from attacker-controlled array32, str32, and bin32 declared sizes before confirming that corresponding elements or bytes were available. A short MessagePack header could therefore trigger a very large allocation or sustained heap growth when an application decoded untrusted input through MessagePack.unpack or MessagePack::Unpacker, potentially exhausting the shared JVM heap. map32 and declared counts at or above 2^31 did not use the affected allocation behavior. This issue is fixed in version 1.8.7.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-15","score":0.00527,"percentile":0.45192,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-1325","CWE-770"],"published":"2026-11-12T22:41:38Z","modified":"2026-11-16T02:34:09Z","fixes":[{"ecosystem":"RubyGems","package":"msgpack","fixed_in":["1.8.7"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"RubyGems","package":"msgpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.8.6"},{"fixed":"1.8.7"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"rubygem-msgpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.8.4-1"}]}]},{"source":"osv","ecosystem":"Docker Hardened Images:Alpine:3.24","package":"gitlab-rails-18","versions":["18.11.11-r0","18.11.11-r1","18.11.11-r2","18.11.12-r0","18.11.12-r1","18.11.12-r2","18.11.12-r3","18.11.12-r4","18.11.14-r0","18.11.14-r1","18.11.14-r10","18.11.14-r11","18.11.14-r2","18.11.14-r3","18.11.14-r4","18.11.14-r5","18.11.14-r6","18.11.14-r7","18.11.14-r8","18.11.14-r9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Alpine:3.24","package":"gitlab-rails-19","versions":["19.1.8-r0","19.1.8-r1","19.4.1-r0","19.4.1-r1","19.4.1-r2","19.4.1-r3","19.4.2-r0","19.5.3-r0","19.5.3-r1","19.5.3-r2","19.5.3-r3","19.5.3-r4","19.5.3-r5","19.5.3-r6","19.5.3-r7","19.5.3-r8","19.5.4-r0","19.5.4-r1","19.5.5-r0","19.5.5-r1","19.5.5-r2"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-1.19-dev","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-1.19-oci-config","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-1.20-dev","versions":["1.20.0-0","1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-1.20-oci-config","versions":["1.20.0-0","1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-1.20","versions":["1.20.0-0","1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-dev","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-27","1.19.3-28","1.19.3-29","1.19.3-3","1.19.3-30","1.19.3-31","1.19.3-32","1.19.3-33","1.19.3-34","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-azureblob-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-azureblob-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-azureblob","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-cloudwatch-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-cloudwatch-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-cloudwatch","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-datadog-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-datadog-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-datadog","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-elasticsearch7-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-elasticsearch7-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-elasticsearch7","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-elasticsearch8-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-elasticsearch8-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-elasticsearch8","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-forward-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-forward-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-forward","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-gcs-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-gcs-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-gcs","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-graylog-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-graylog-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-graylog","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-kafka-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-kafka-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-kafka2-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-kafka2-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-kafka2","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-kafka","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-kinesis-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-kinesis-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-kinesis","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-logentries-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-logentries-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-logentries","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-loggly-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-loggly-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-loggly","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-logzio-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-logzio-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-logzio","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-opensearch-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-opensearch-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-opensearch","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-papertrail-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-papertrail-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-papertrail","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-s3-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-s3-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-s3","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-syslog-1.19","versions":["1.19.4-8","1.19.4-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-syslog-1.20","versions":["1.20.1-0","1.20.1-1"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-kubernetes-daemonset-syslog","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-3","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd-oci-config","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-27","1.19.3-28","1.19.3-29","1.19.3-3","1.19.3-30","1.19.3-31","1.19.3-32","1.19.3-33","1.19.3-34","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"fluentd","versions":["1.19.3-0","1.19.3-1","1.19.3-10","1.19.3-11","1.19.3-12","1.19.3-13","1.19.3-14","1.19.3-15","1.19.3-16","1.19.3-17","1.19.3-18","1.19.3-19","1.19.3-2","1.19.3-20","1.19.3-21","1.19.3-22","1.19.3-23","1.19.3-24","1.19.3-25","1.19.3-26","1.19.3-27","1.19.3-28","1.19.3-29","1.19.3-3","1.19.3-30","1.19.3-31","1.19.3-32","1.19.3-33","1.19.3-34","1.19.3-4","1.19.3-5","1.19.3-6","1.19.3-7","1.19.3-8","1.19.3-9","1.19.4-0","1.19.4-1","1.19.4-2","1.19.4-3","1.19.4-4","1.19.4-5","1.19.4-6","1.19.4-7","1.19.4-8"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"gitlab-rails-18","versions":["18.11.11-0","18.11.11-1","18.11.11-2","18.11.12-0","18.11.12-1","18.11.12-2","18.11.14-0","18.11.14-1","18.11.14-10","18.11.14-11","18.11.14-12","18.11.14-13","18.11.14-14","18.11.14-15","18.11.14-16","18.11.14-2","18.11.14-3","18.11.14-4","18.11.14-5","18.11.14-6","18.11.14-7","18.11.14-8","18.11.14-9"]},{"source":"osv","ecosystem":"Docker Hardened Images:Debian:13","package":"gitlab-rails-19","versions":["19.1.8-0","19.1.8-1","19.4.1-0","19.4.1-1","19.4.1-2","19.4.2-0","19.5.3-0","19.5.3-1","19.5.3-2","19.5.3-3","19.5.3-4","19.5.3-5","19.5.3-6","19.5.3-7","19.5.3-8","19.5.3-9","19.5.4-0","19.5.4-1","19.5.5-0","19.5.5-1","19.5.5-2","19.5.5-3","19.5.5-4","19.5.5-5","19.5.5-6"]},{"source":"osv","ecosystem":"RubyGems","package":"msgpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.8.7"}]}],"versions":["0.0.1","0.2.0","0.2.1","0.2.2","0.3.0","0.3.1","0.3.2","0.3.3","0.3.4","0.3.5","0.3.6","0.3.7","0.3.8","0.3.9","0.4.0","0.4.1","0.4.2","0.4.3","0.4.4","0.4.5","0.4.6","0.4.7","0.5.0","0.5.1","0.5.10","0.5.11","0.5.12","0.5.2","0.5.3","0.5.4","0.5.5","0.5.6","0.5.7","0.5.8","0.5.9","0.6.0","0.6.0pre1","0.6.1","0.6.2","0.7.0","0.7.0dev1","0.7.1","0.7.2","0.7.2dev1","0.7.3","0.7.4","0.7.5","0.7.6","1.0.0","1.0.1","1.0.2","1.0.3","1.1.0","1.2.0","1.2.1","1.2.10","1.2.2","1.2.3","1.2.4","1.2.5","1.2.6","1.2.7","1.2.8","1.2.9","1.3.0","1.3.1","1.3.2","1.3.3","1.4.0","1.4.0.pre1","1.4.1","1.4.2","1.4.3","1.4.4","1.4.4.pre1","1.4.5","1.5.0","1.5.1","1.5.2","1.5.3","1.5.4","1.5.5","1.5.6","1.6.0","1.6.1","1.7.0","1.7.1","1.7.2","1.7.3","1.7.4","1.7.5","1.8.0","1.8.1","1.8.2","1.8.3","1.8.4","1.8.5","1.8.6"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"ruby-msgpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.6.2-1build1","0.6.2-1build2","0.6.2-1build3","0.6.2-1build4"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"ruby-msgpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.0.0-1","1.1.0-1","1.1.0-1build1","1.1.0-1build2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"ruby-msgpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.1.0-1build2","1.1.0-1build3"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"ruby-msgpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.1.0-2build1","1.1.0-2build2","1.4.2-2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"ruby-msgpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.4.2-2build2","1.4.2-2build3","1.4.2-2build4"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"ruby-msgpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.8.0-1","1.8.3-1","1.8.4-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"ruby-msgpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.7.2-1.1","1.8.0-1"]}],"products":[{"vendor":"msgpack","product":"msgpack-ruby"}],"references":[{"url":"https://github.com/msgpack/msgpack-ruby/security/advisories/GHSA-73v3-wf97-vpgj","tags":["x_refsource_CONFIRM","advisory","web","report"]},{"url":"https://github.com/msgpack/msgpack-ruby/commit/ca0efc1256c687b428c46dd68ce000ff515d53f2","tags":["x_refsource_MISC","fix","web","report"]},{"url":"https://github.com/msgpack/msgpack-ruby/releases/tag/v1.8.6","tags":["x_refsource_MISC","web","report"]},{"url":"https://github.com/msgpack/msgpack-ruby/releases/tag/v1.8.7","tags":["x_refsource_MISC","web","report"]},{"url":"https://github.com/advisories/GHSA-73v3-wf97-vpgj","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-126366","tags":["web","advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/126xxx/CVE-2026-126366.json","tags":["advisory"]},{"url":"https://scout.docker.com/v/DHI-4lzs-kcmy-bnh7-x5g2","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-126366","tags":["advisory","report"]},{"url":"http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-126366","tags":["advisory"]},{"url":"https://github.com/msgpack/msgpack-ruby","tags":["package"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-126366","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-126366","title":"msgpack-java JRuby decoder allocates from declared header counts with no cap: 5-byte message forces multi-GiB OOM","description":"MessagePack for Ruby is an implementation of the MessagePack binary serialization format. Prior to 1.8.7, the Java-platform msgpack gem for JRuby allocated arrays and byte buffers directly from attacker-controlled array32, str32, and bin32 declared sizes before confirming that corresponding elements or bytes were available. A short MessagePack header could therefore trigger a very large allocation or sustained heap growth when an application decoded untrusted input through MessagePack.unpack or MessagePack::Unpacker, potentially exhausting the shared JVM heap. map32 and declared counts at or above 2^31 did not use the affected allocation behavior. This issue is fixed in version 1.8.7.","status":"published","published":"2026-11-12T22:41:38.409Z","modified":"2026-11-13T22:32:11.586Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"cna"}],"cwes":["CWE-770","CWE-1325"],"updated_at":"2026-11-12T23:50:00.469154Z"}],"euvd":[{"id":"EUVD-2026-124750","description":"MessagePack for Ruby is an implementation of the MessagePack binary serialization format. Prior to 1.8.7, the Java-platform msgpack gem for JRuby allocated arrays and byte buffers directly from attacker-controlled array32, str32, and bin32 declared sizes before confirming that corresponding elements or bytes were available. A short MessagePack header could therefore trigger a very large allocation or sustained heap growth when an application decoded untrusted input through MessagePack.unpack or MessagePack::Unpacker, potentially exhausting the shared JVM heap. map32 and declared counts at or above 2^31 did not use the affected allocation behavior. This issue is fixed in version 1.8.7.","status":"published","published":"2026-11-12T22:41:38Z","modified":"2026-11-13T22:32:11Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-13T23:41:01.258782Z"}],"ghsa":[{"id":"GHSA-73v3-wf97-vpgj","title":"msgpack-ruby JRuby decoder makes uncapped header-count allocations; a 5-byte message forces multi-GiB OOM","description":"### Summary\n\nThe **JRuby** implementation of msgpack (`msgpack` gem, `java` platform — pure Java decoder under `ext/java/`) sizes containers directly from the element count written in the message header, with **no cap at all**: no equivalent of the C unpacker's `SHRT_MAX` clamp (since 1.7.3) and none of the buffered-bytes cap that commit c8d42d8 added for CRuby in 1.8.6. A single 5-byte message decides how much memory a JVM process tries to allocate:\n\n* `array32` header declaring `0x7FFFFFFF` elements → `new IRubyObject[0x7FFFFFFF]` (~8 GiB of reference slots) attempted immediately → `java.lang.OutOfMemoryError: Requested array size exceeds VM limit`.\n* Counts *below* the VM's max-array-size but above available heap (e.g. 5×10⁸ with a 512 MiB heap) produce a **real allocation attempt** — `OutOfMemoryError: Java heap space` — the JVM genuinely tries to take the memory before failing.\n* `str32`/`bin32` headers declaring `0x7FFFFFFF` bytes do the same via `readBytes(size)` → `new byte[size]`.\n* Below the failure threshold there is a **silent band**: one streaming unpacker fed only an `array32` header with count 2×10⁷ (5 wire bytes, zero elements) grows used heap **+78 MiB immediately**, no exception (`each` swallows the underflow), and the footprint stays elevated after `Unpacker#reset` + full GC. Linear in declared count (~4 B/element); nothing bounds it — not delivered bytes, not a per-container cap.\n\nOnly counts ≥ 2³¹ are refused (a clean `MessagePack::UnderflowError` from `getUnsignedInt()`), and only **maps** are safe (`consumeHash` grows per element instead of pre-sizing). Verified on the released gem `msgpack 1.8.6 java`, JRuby 9.4.12 / OpenJDK 25, 2026-10-30 — i.e. **unfixed in the current release**. Proposed fix mirrors c8d42d8: cap initial allocation by bytes actually buffered and grow as data arrives; read strings in bounded chunks instead of allocating the declared length up front.\n\n\n### Details\n\n### 1. The four dispatch arms, and which pre-allocate (line numbers at tag v1.8.6 — current release; `ext/java` has no commits after it)\n\n| header | dispatch ([Decoder.java](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java)) | behaviour on the declared count | measured (released 1.8.6-java, Xmx512m) |\n|---|---|---|---|\n| `array32` `\\xdd` | [:296](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L296) → [`consumeArray(int size)` :139-145](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L139-L145) | `new IRubyObject[size]` **immediately**, before reading any element | count `0x7FFFFFFF`: OOME \"Requested array size exceeds VM limit\"; count 5×10⁸: OOME \"**Java heap space**\" (real allocation attempt); count 2×10⁷: **+78 MiB, silent** |\n| `str32` `\\xdb` | [:294](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L294) → [`consumeString` :129](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L129) → [`readBytes(int size)` :186-190](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L186-L190) | `new byte[size]` **immediately** | len `0x7FFFFFFF`: OOME \"array size exceeds VM limit\" |\n| `bin32` `\\xc6` | [:269](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L269) → same `consumeString`/`readBytes` | same | len `0x7FFFFFFF`: OOME \"array size exceeds VM limit\" |\n| `map32` `\\xdf` | [:298](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L298) → [`consumeHash(int size)` :147+](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L147) | **no pre-allocation** — inserts per element, underflows on first missing byte | count `0x7FFFFFFF`: no exception (swallowed), no large allocation |\n\nThe only guard is [`getUnsignedInt()` :88-94](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L88-L94): counts with the top bit set (≥ 2³¹) raise `MessagePack::UnderflowError: Size too large (limited to 2**31 for the Java version)`. That bounds the *value* but leaves the entire positive band `(available heap, 2³¹)` unbounded — and that band is where real allocation attempts happen.\n\n### 2. Contrast with the C implementation (same repo)\n\nThe CRuby unpacker has had a per-container cap since 1.7.3 (`INITIAL_BUFFER_CAPACITY_MAX = SHRT_MAX`) and, since [c8d42d8](https://github.com/msgpack/msgpack-ruby/commit/c8d42d8) in **1.8.6**, additionally caps initial size by bytes actually buffered (\"an element needs at least one byte…\"). Strings on C are bounded too (`read_raw_body_cont` allocates `min(remaining, buffered)`). The Java decoder has **neither generation of cap** — it is strictly behind the CRuby behaviour this repo already considers correct enough to ship.\n\n### 3. Silent retention + mechanism control (measured 2026-10-30, released gem)\n\nOne `MessagePack::Unpacker` per process, fed only a header (`\"\\xdd\" + [count].pack('N')`), zero elements; heap = `Runtime.total_memory - free_memory` after `GC.start` on both sides:\n\n| declared count | used heap before → after | delta | exception? |\n|---|---|---|---|\n| 1,000,000 | 26.4 → 31.1 MiB | +4.7 | none (`each` swallows the underflow) |\n| 5,000,000 | 53.3 → 74.0 MiB | +20.7 | none |\n| 20,000,000 | 51.3 → 129.3 MiB | **+78.0** | none |\n\nMechanism control: after the feed, `Unpacker#reset` + three `GC.start` cycles left used heap at **+79.4 MiB above baseline** (2×10⁷ arm) — the elevation is *not* unpacker-held state; it is JVM heap already spent on header-declared allocation and not returned. Either way the process footprint grows per attack and stays grown; the peak cost is paid synchronously during parsing regardless of GC behaviour afterwards. (Honest scope note: this is unbounded **allocation**, not a memory leak.)\n\n### 4. Why JVM makes availability impact worse than the CRuby analogue\n\nIn CRuby, allocation failure raises `NoMemoryError`/fails inside one worker process. In a JVM, an OOME raised on the parser thread can land anywhere in the host application's shared runtime — long-lived JRuby servers (Rails, Logstash-class pipelines, JDBC apps) share heap across all threads and connections; a single crafted message can destabilize or kill the whole JVM, not just the request. The silent band means no exception at all is even required to spend memory.\n\n### 5. Not claimed / scope\n\n* **Fluentd is NOT affected** (and this report deliberately does not involve it): Fluentd ships CRuby-only — CI pins `engine: cruby`, gemspec requires ruby \u003e= 3.3 while JRuby 9.4 implements Ruby 3.1 semantics, and there are zero JRUBY guards in lib/. This is an upstream msgpack-ruby report only.\n* Maps (`map32`) do not pre-allocate — measured; the class applies to `array32`/`str32`/`bin32`.\n* Counts ≥ 2³¹ are cleanly refused — measured; no claim there.\n* Older java-gem releases were not individually probed; `\u003c= 1.8.6` means \"every release up to the current one carries this code\".\n\n\n### Proof of concept\n\nVerified on the **released gem** `msgpack 1.8.6 java`, JRuby 9.4.12.0, OpenJDK 25.0.4.1, Linux x86-64 (artifacts in `evidence_186_recheck/`). Always run with a small `-Xmx` so oversized requests fail fast instead of wrecking the box.\n\n### Setup\n\n```console\n$ curl -fsSLO https://repo1.maven.org/maven2/org/jruby/jruby-dist/9.4.12.0/jruby-dist-9.4.12.0-bin.tar.gz\n$ tar xzf jruby-dist-9.4.12.0-bin.tar.gz \u0026\u0026 export PATH=$PWD/jruby-9.4.12.0/bin:$PATH\n$ jruby -S gem install msgpack --no-document      # resolves the java-platform gem: \"msgpack (1.8.6 java)\"\n```\n\n### 1. Header shapes (fresh process per arm, `-Xmx512m`)\n\n```console\narray32 count=0xFFFFFFFF       -\u003e MessagePack::UnderflowError: Size too large (limited to 2**31 for the Java version)\narray32 count=0x7FFFFFFF       -\u003e Java::JavaLang::OutOfMemoryError: Requested array size exceeds VM limit\narray32 count=500000000        -\u003e Java::JavaLang::OutOfMemoryError: Java heap space   # real allocation attempt\nstr32   len=0x7FFFFFFF         -\u003e Java::JavaLang::OutOfMemoryError: Requested array size exceeds VM limit\nbin32   len=0x7FFFFFFF         -\u003e Java::JavaLang::OutOfMemoryError: Requested array size exceeds VM limit\nmap32   count=0x7FFFFFFF       -\u003e no exception, no large allocation (consumeHash grows per element)\n```\n\nEach payload is five bytes, e.g. `\"\\xdd\" + [count].pack('N')` fed to `MessagePack::Unpacker#feed_each`. Scripts: `jr_probe.rb`, `jr_probe_extra.rb` (attached in kit).\n\n### 2. Silent band — retention from one header (Xmx1g)\n\n```console\n$ for n in 1000000 5000000 20000000; do jruby -J-Xmx1g jr_one.rb $n; done\ncount=  1000000 heap 26.4 -\u003e 31.1 MiB (delta 4.7)   | no exception (underflow swallowed)\ncount=  5000000 heap 53.3 -\u003e 74.0 MiB (delta 20.7)  | no exception (underflow swallowed)\ncount= 20000000 heap 51.3 -\u003e 129.3 MiB (delta 78.0) | no exception (underflow swallowed)\n\n$ jruby -J-Xmx1g jr_reset_control.rb 20000000\ncount=20000000 heap base=49.9 after_feed=129.3 (delta 79.4) after_reset_gc=129.3 (retained_vs_base 79.4)\n```\n\nA streaming server that keeps one unpacker per connection (the pattern any socket-fed msgpack service uses) pays this per connection with five wire bytes each and produces no exception, no log line.\n\n### 3. Fix verification path\n\nApply the C-side idea from c8d42d8: in `consumeArray`, cap the initial array by bytes actually buffered (an element needs ≥ 1 byte) and grow as elements arrive; in `readBytes`/`consumeString`, read in bounded chunks instead of allocating the declared length up front. Then re-run this PoC: the silent band should track delivered bytes, and oversized declarations should raise `UnderflowError`-class errors without touching multi-GiB allocations. msgpack-ruby CI runs jruby-9.4/truffleruby, so a patch is verifiable as-is; I can prepare one against `ext/java/org/msgpack/jruby/Decoder.java`.\n\n\n### Impact\n\n**Type.** Uncontrolled resource consumption driven by *declared* sizes rather than delivered bytes — CWE-770 (Allocation of Resources Without Limits or Throttling), precisely CWE-1325 (Independent Resource Usage Limiting Not Applied). Availability only; no confidentiality/integrity impact, no code execution.\n\n**Who is impacted.** Any JRuby application that feeds untrusted msgpack to `MessagePack.unpack`/`Unpacker` — the java-platform gem's whole user base (JRuby-based services, log/RPC pipelines, JVM polyglot stacks using this gem). For them: remote OOM of a shared-heap JVM from a 5-byte message, or silent heap spend below the exception band.\n\n**Severity.** Proposed **High / 7.5**, `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` — remote, trivially crafted, default settings, process death; same metric string as the accepted fluentd OOM family (e.g. GHSA-h3xv-5jpx-r4j2) and as this repo's own C-side analogue (reported separately, patched at 1.8.6). If triage weighs the platform scope (java gem only), lower framings read against that — we flag it honestly; the maintainers' call on scope shouldn't delay the patch.\n\n**Relationship to the C-side report.** Same flaw class, different implementation and fix state: CRuby's pre-allocation was capped by c8d42d8 (released 1.8.6, separate advisory with affected `\u003c= 1.8.5`, patched `1.8.6`). This JRuby variant is **unfixed in 1.8.6** and needs its own patch + CVE. Cross-reference both ways once filed.\n\n**What this is not.** Not a Fluentd issue (Fluentd is CRuby-only — CI pins cruby, gemspec ruby \u003e= 3.3 vs JRuby's Ruby 3.1 semantics); no fluentd advisory should carry this. Not a memory leak (measured: footprint elevation persists after reset+GC without retained objects). Not exploitable via maps or counts ≥ 2³¹ (both measured safe/cleanly refused).","status":"published","published":"2026-11-12T22:54:59Z","modified":"2026-11-12T22:55:00Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-770","CWE-1325"],"updated_at":"2026-11-12T23:14:04.864964Z"}],"nvd":[{"id":"CVE-2026-126366","description":"MessagePack for Ruby is an implementation of the MessagePack binary serialization format. Prior to 1.8.7, the Java-platform msgpack gem for JRuby allocated arrays and byte buffers directly from attacker-controlled array32, str32, and bin32 declared sizes before confirming that corresponding elements or bytes were available. A short MessagePack header could therefore trigger a very large allocation or sustained heap growth when an application decoded untrusted input through MessagePack.unpack or MessagePack::Unpacker, potentially exhausting the shared JVM heap. map32 and declared counts at or above 2^31 did not use the affected allocation behavior. This issue is fixed in version 1.8.7.","status":"published","published":"2026-11-13T00:20:12.397Z","modified":"2026-11-13T23:17:16.49Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"secondary"}],"cwes":["CWE-770","CWE-1325"],"updated_at":"2026-11-13T01:33:42.076678Z"}],"osv":[{"id":"CVE-2026-126366","title":"msgpack-java JRuby decoder allocates from declared header counts with no cap: 5-byte message forces multi-GiB OOM","description":"MessagePack for Ruby is an implementation of the MessagePack binary serialization format. Prior to 1.8.7, the Java-platform msgpack gem for JRuby allocated arrays and byte buffers directly from attacker-controlled array32, str32, and bin32 declared sizes before confirming that corresponding elements or bytes were available. A short MessagePack header could therefore trigger a very large allocation or sustained heap growth when an application decoded untrusted input through MessagePack.unpack or MessagePack::Unpacker, potentially exhausting the shared JVM heap. map32 and declared counts at or above 2^31 did not use the affected allocation behavior. This issue is fixed in version 1.8.7.","status":"published","published":"2026-11-12T22:41:38.409Z","modified":"2026-11-15T07:04:25.966336812Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-1325","CWE-770"],"updated_at":"2026-11-14T03:11:06.681237Z"},{"id":"DHI-4lzs-kcmy-bnh7-x5g2","title":"MessagePack for Ruby is an implementation of the MessagePack binary serialization format. Prior to 1.8.7, the…","description":"MessagePack for Ruby is an implementation of the MessagePack binary serialization format. Prior to 1.8.7, the Java-platform msgpack gem for JRuby allocated arrays and byte buffers directly from attacker-controlled array32, str32, and bin32 declared sizes before confirming that corresponding elements or bytes were available. A short MessagePack header could therefore trigger a very large allocation or sustained heap growth when an application decoded untrusted input through MessagePack.unpack or MessagePack::Unpacker, potentially exhausting the shared JVM heap. map32 and declared counts at or above 2^31 did not use the affected allocation behavior. This issue is fixed in version 1.8.7.","status":"published","published":"2026-11-13T17:07:20Z","modified":"2026-11-16T02:34:09.100395105Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-16T03:08:59.598406Z"},{"id":"GHSA-73v3-wf97-vpgj","title":"msgpack-ruby JRuby decoder makes uncapped header-count allocations; a 5-byte message forces multi-GiB OOM","description":"### Summary\n\nThe **JRuby** implementation of msgpack (`msgpack` gem, `java` platform — pure Java decoder under `ext/java/`) sizes containers directly from the element count written in the message header, with **no cap at all**: no equivalent of the C unpacker's `SHRT_MAX` clamp (since 1.7.3) and none of the buffered-bytes cap that commit c8d42d8 added for CRuby in 1.8.6. A single 5-byte message decides how much memory a JVM process tries to allocate:\n\n* `array32` header declaring `0x7FFFFFFF` elements → `new IRubyObject[0x7FFFFFFF]` (~8 GiB of reference slots) attempted immediately → `java.lang.OutOfMemoryError: Requested array size exceeds VM limit`.\n* Counts *below* the VM's max-array-size but above available heap (e.g. 5×10⁸ with a 512 MiB heap) produce a **real allocation attempt** — `OutOfMemoryError: Java heap space` — the JVM genuinely tries to take the memory before failing.\n* `str32`/`bin32` headers declaring `0x7FFFFFFF` bytes do the same via `readBytes(size)` → `new byte[size]`.\n* Below the failure threshold there is a **silent band**: one streaming unpacker fed only an `array32` header with count 2×10⁷ (5 wire bytes, zero elements) grows used heap **+78 MiB immediately**, no exception (`each` swallows the underflow), and the footprint stays elevated after `Unpacker#reset` + full GC. Linear in declared count (~4 B/element); nothing bounds it — not delivered bytes, not a per-container cap.\n\nOnly counts ≥ 2³¹ are refused (a clean `MessagePack::UnderflowError` from `getUnsignedInt()`), and only **maps** are safe (`consumeHash` grows per element instead of pre-sizing). Verified on the released gem `msgpack 1.8.6 java`, JRuby 9.4.12 / OpenJDK 25, 2026-10-30 — i.e. **unfixed in the current release**. Proposed fix mirrors c8d42d8: cap initial allocation by bytes actually buffered and grow as data arrives; read strings in bounded chunks instead of allocating the declared length up front.\n\n\n### Details\n\n### 1. The four dispatch arms, and which pre-allocate (line numbers at tag v1.8.6 — current release; `ext/java` has no commits after it)\n\n| header | dispatch ([Decoder.java](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java)) | behaviour on the declared count | measured (released 1.8.6-java, Xmx512m) |\n|---|---|---|---|\n| `array32` `\\xdd` | [:296](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L296) → [`consumeArray(int size)` :139-145](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L139-L145) | `new IRubyObject[size]` **immediately**, before reading any element | count `0x7FFFFFFF`: OOME \"Requested array size exceeds VM limit\"; count 5×10⁸: OOME \"**Java heap space**\" (real allocation attempt); count 2×10⁷: **+78 MiB, silent** |\n| `str32` `\\xdb` | [:294](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L294) → [`consumeString` :129](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L129) → [`readBytes(int size)` :186-190](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L186-L190) | `new byte[size]` **immediately** | len `0x7FFFFFFF`: OOME \"array size exceeds VM limit\" |\n| `bin32` `\\xc6` | [:269](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L269) → same `consumeString`/`readBytes` | same | len `0x7FFFFFFF`: OOME \"array size exceeds VM limit\" |\n| `map32` `\\xdf` | [:298](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L298) → [`consumeHash(int size)` :147+](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L147) | **no pre-allocation** — inserts per element, underflows on first missing byte | count `0x7FFFFFFF`: no exception (swallowed), no large allocation |\n\nThe only guard is [`getUnsignedInt()` :88-94](https://github.com/msgpack/msgpack-ruby/blob/v1.8.6/ext/java/org/msgpack/jruby/Decoder.java#L88-L94): counts with the top bit set (≥ 2³¹) raise `MessagePack::UnderflowError: Size too large (limited to 2**31 for the Java version)`. That bounds the *value* but leaves the entire positive band `(available heap, 2³¹)` unbounded — and that band is where real allocation attempts happen.\n\n### 2. Contrast with the C implementation (same repo)\n\nThe CRuby unpacker has had a per-container cap since 1.7.3 (`INITIAL_BUFFER_CAPACITY_MAX = SHRT_MAX`) and, since [c8d42d8](https://github.com/msgpack/msgpack-ruby/commit/c8d42d8) in **1.8.6**, additionally caps initial size by bytes actually buffered (\"an element needs at least one byte…\"). Strings on C are bounded too (`read_raw_body_cont` allocates `min(remaining, buffered)`). The Java decoder has **neither generation of cap** — it is strictly behind the CRuby behaviour this repo already considers correct enough to ship.\n\n### 3. Silent retention + mechanism control (measured 2026-10-30, released gem)\n\nOne `MessagePack::Unpacker` per process, fed only a header (`\"\\xdd\" + [count].pack('N')`), zero elements; heap = `Runtime.total_memory - free_memory` after `GC.start` on both sides:\n\n| declared count | used heap before → after | delta | exception? |\n|---|---|---|---|\n| 1,000,000 | 26.4 → 31.1 MiB | +4.7 | none (`each` swallows the underflow) |\n| 5,000,000 | 53.3 → 74.0 MiB | +20.7 | none |\n| 20,000,000 | 51.3 → 129.3 MiB | **+78.0** | none |\n\nMechanism control: after the feed, `Unpacker#reset` + three `GC.start` cycles left used heap at **+79.4 MiB above baseline** (2×10⁷ arm) — the elevation is *not* unpacker-held state; it is JVM heap already spent on header-declared allocation and not returned. Either way the process footprint grows per attack and stays grown; the peak cost is paid synchronously during parsing regardless of GC behaviour afterwards. (Honest scope note: this is unbounded **allocation**, not a memory leak.)\n\n### 4. Why JVM makes availability impact worse than the CRuby analogue\n\nIn CRuby, allocation failure raises `NoMemoryError`/fails inside one worker process. In a JVM, an OOME raised on the parser thread can land anywhere in the host application's shared runtime — long-lived JRuby servers (Rails, Logstash-class pipelines, JDBC apps) share heap across all threads and connections; a single crafted message can destabilize or kill the whole JVM, not just the request. The silent band means no exception at all is even required to spend memory.\n\n### 5. Not claimed / scope\n\n* **Fluentd is NOT affected** (and this report deliberately does not involve it): Fluentd ships CRuby-only — CI pins `engine: cruby`, gemspec requires ruby \u003e= 3.3 while JRuby 9.4 implements Ruby 3.1 semantics, and there are zero JRUBY guards in lib/. This is an upstream msgpack-ruby report only.\n* Maps (`map32`) do not pre-allocate — measured; the class applies to `array32`/`str32`/`bin32`.\n* Counts ≥ 2³¹ are cleanly refused — measured; no claim there.\n* Older java-gem releases were not individually probed; `\u003c= 1.8.6` means \"every release up to the current one carries this code\".\n\n\n### Proof of concept\n\nVerified on the **released gem** `msgpack 1.8.6 java`, JRuby 9.4.12.0, OpenJDK 25.0.4.1, Linux x86-64 (artifacts in `evidence_186_recheck/`). Always run with a small `-Xmx` so oversized requests fail fast instead of wrecking the box.\n\n### Setup\n\n```console\n$ curl -fsSLO https://repo1.maven.org/maven2/org/jruby/jruby-dist/9.4.12.0/jruby-dist-9.4.12.0-bin.tar.gz\n$ tar xzf jruby-dist-9.4.12.0-bin.tar.gz \u0026\u0026 export PATH=$PWD/jruby-9.4.12.0/bin:$PATH\n$ jruby -S gem install msgpack --no-document      # resolves the java-platform gem: \"msgpack (1.8.6 java)\"\n```\n\n### 1. Header shapes (fresh process per arm, `-Xmx512m`)\n\n```console\narray32 count=0xFFFFFFFF       -\u003e MessagePack::UnderflowError: Size too large (limited to 2**31 for the Java version)\narray32 count=0x7FFFFFFF       -\u003e Java::JavaLang::OutOfMemoryError: Requested array size exceeds VM limit\narray32 count=500000000        -\u003e Java::JavaLang::OutOfMemoryError: Java heap space   # real allocation attempt\nstr32   len=0x7FFFFFFF         -\u003e Java::JavaLang::OutOfMemoryError: Requested array size exceeds VM limit\nbin32   len=0x7FFFFFFF         -\u003e Java::JavaLang::OutOfMemoryError: Requested array size exceeds VM limit\nmap32   count=0x7FFFFFFF       -\u003e no exception, no large allocation (consumeHash grows per element)\n```\n\nEach payload is five bytes, e.g. `\"\\xdd\" + [count].pack('N')` fed to `MessagePack::Unpacker#feed_each`. Scripts: `jr_probe.rb`, `jr_probe_extra.rb` (attached in kit).\n\n### 2. Silent band — retention from one header (Xmx1g)\n\n```console\n$ for n in 1000000 5000000 20000000; do jruby -J-Xmx1g jr_one.rb $n; done\ncount=  1000000 heap 26.4 -\u003e 31.1 MiB (delta 4.7)   | no exception (underflow swallowed)\ncount=  5000000 heap 53.3 -\u003e 74.0 MiB (delta 20.7)  | no exception (underflow swallowed)\ncount= 20000000 heap 51.3 -\u003e 129.3 MiB (delta 78.0) | no exception (underflow swallowed)\n\n$ jruby -J-Xmx1g jr_reset_control.rb 20000000\ncount=20000000 heap base=49.9 after_feed=129.3 (delta 79.4) after_reset_gc=129.3 (retained_vs_base 79.4)\n```\n\nA streaming server that keeps one unpacker per connection (the pattern any socket-fed msgpack service uses) pays this per connection with five wire bytes each and produces no exception, no log line.\n\n### 3. Fix verification path\n\nApply the C-side idea from c8d42d8: in `consumeArray`, cap the initial array by bytes actually buffered (an element needs ≥ 1 byte) and grow as elements arrive; in `readBytes`/`consumeString`, read in bounded chunks instead of allocating the declared length up front. Then re-run this PoC: the silent band should track delivered bytes, and oversized declarations should raise `UnderflowError`-class errors without touching multi-GiB allocations. msgpack-ruby CI runs jruby-9.4/truffleruby, so a patch is verifiable as-is; I can prepare one against `ext/java/org/msgpack/jruby/Decoder.java`.\n\n\n### Impact\n\n**Type.** Uncontrolled resource consumption driven by *declared* sizes rather than delivered bytes — CWE-770 (Allocation of Resources Without Limits or Throttling), precisely CWE-1325 (Independent Resource Usage Limiting Not Applied). Availability only; no confidentiality/integrity impact, no code execution.\n\n**Who is impacted.** Any JRuby application that feeds untrusted msgpack to `MessagePack.unpack`/`Unpacker` — the java-platform gem's whole user base (JRuby-based services, log/RPC pipelines, JVM polyglot stacks using this gem). For them: remote OOM of a shared-heap JVM from a 5-byte message, or silent heap spend below the exception band.\n\n**Severity.** Proposed **High / 7.5**, `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` — remote, trivially crafted, default settings, process death; same metric string as the accepted fluentd OOM family (e.g. GHSA-h3xv-5jpx-r4j2) and as this repo's own C-side analogue (reported separately, patched at 1.8.6). If triage weighs the platform scope (java gem only), lower framings read against that — we flag it honestly; the maintainers' call on scope shouldn't delay the patch.\n\n**Relationship to the C-side report.** Same flaw class, different implementation and fix state: CRuby's pre-allocation was capped by c8d42d8 (released 1.8.6, separate advisory with affected `\u003c= 1.8.5`, patched `1.8.6`). This JRuby variant is **unfixed in 1.8.6** and needs its own patch + CVE. Cross-reference both ways once filed.\n\n**What this is not.** Not a Fluentd issue (Fluentd is CRuby-only — CI pins cruby, gemspec ruby \u003e= 3.3 vs JRuby's Ruby 3.1 semantics); no fluentd advisory should carry this. Not a memory leak (measured: footprint elevation persists after reset+GC without retained objects). Not exploitable via maps or counts ≥ 2³¹ (both measured safe/cleanly refused).","status":"published","published":"2026-11-12T22:54:59Z","modified":"2026-11-12T23:00:05.611968338Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-1325","CWE-770"],"updated_at":"2026-11-12T23:17:33.063883Z"},{"id":"UBUNTU-CVE-2026-126366","description":"MessagePack for Ruby is an implementation of the MessagePack binary serialization format. Prior to 1.8.7, the Java-platform msgpack gem for JRuby allocated arrays and byte buffers directly from attacker-controlled array32, str32, and bin32 declared sizes before confirming that corresponding elements or bytes were available. A short MessagePack header could therefore trigger a very large allocation or sustained heap growth when an application decoded untrusted input through MessagePack.unpack or MessagePack::Unpacker, potentially exhausting the shared JVM heap. map32 and declared counts at or above 2^31 did not use the affected allocation behavior. This issue is fixed in version 1.8.7.","status":"published","published":"2026-11-13T00:00:00Z","modified":"2026-11-13T21:05:26.064051945Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-13T21:30:20.292037Z"},{"id":"AZL-114061","title":"CVE-2026-126366 affecting package rubygem-msgpack 1.8.4-1","description":"MessagePack for Ruby is an implementation of the MessagePack binary serialization format. Prior to 1.8.7, the Java-platform msgpack gem for JRuby allocated arrays and byte buffers directly from attacker-controlled array32, str32, and bin32 declared sizes before confirming that corresponding elements or bytes were available. A short MessagePack header could therefore trigger a very large allocation or sustained heap growth when an application decoded untrusted input through MessagePack.unpack or MessagePack::Unpacker, potentially exhausting the shared JVM heap. map32 and declared counts at or above 2^31 did not use the affected allocation behavior. This issue is fixed in version 1.8.7.","status":"published","published":"2026-11-13T00:20:12Z","modified":"2026-11-15T14:16:46.825389565Z","updated_at":"2026-11-15T14:49:46.183447Z"}]}}
