Infinispan circular object references causes out of memory errors
CVE-2023-5236GHSA-488m-w9fp-5mm2
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.infinispan.protostream:protostream 4.6.2.Final), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.infinispan.protostream:protostream
- Affected
- < 4.6.2.Final
- Fixed in
- 4.6.2.Final
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-488m-w9fp-5mm2 lists affected ranges: Maven org.infinispan.protostream:protostream >=0 <4.6.2.Final
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2023-5236: 1.11% estimated exploitation activity in the next 30 days; percentile 65.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
A flaw was found in Infinispan, which does not detect circular object references when unmarshalling. An authenticated attacker with sufficient permissions could insert a maliciously constructed object into the cache and use it to cause out of memory errors and achieve a denial of service.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-488m-w9fp-5mm2
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2023-5236 Advisory: Infinispan circular object references causes out of memory errors IDs: CVE-2023-5236, GHSA-488m-w9fp-5mm2 Record: https://patchnext.com/advisories/cve-2023-5236 (revision 1, source checked 26 Oct 2026, 16:31 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.infinispan.protostream:protostream 4.6.2.Final. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.infinispan.protostream:protostream: affected < 4.6.2.Final; fixed in 4.6.2.Final ## Suggested inspection (read-only) - Maven org.infinispan.protostream:protostream: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.infinispan.protostream:protostream. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-488m-w9fp-5mm2 (GitHub-reviewed advisory GHSA-488m-w9fp-5mm2 lists affected ranges: Maven org.infinispan.protostream:protostream >=0 <4.6.2.Final) Commands are suggestions: review each one before running it.
Loading voting…