{"answers":{"affected":"2 open source packages ship an affected version, including org.infinispan:infinispan-parent.","exploited":"There is no known exploitation of CVE-2025-0736 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-0736 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-0736 is a medium-severity vulnerability in Red Hat Data Grid, published on 28 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-0736 and fix it if it is affected.\n\nWhat it is: CVE-2025-0736 is a medium-severity vulnerability in Red Hat Data Grid, published on 28 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-0736 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.infinispan:infinispan-parent (Maven): affected all versions up to 15.1.4.Final; no fix listed\n- org.infinispan:infinispan-parent (Maven): affected all versions up to 15.1.4.Final; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-0736/ (Markdown: https://insights.sbomify.com/CVE-2025-0736/index.md)","id":"CVE-2025-0736","markdown":"https://insights.sbomify.com/CVE-2025-0736/index.md","name":"CVE-2025-0736","record":{"aliases":["GHSA-269m-c36j-r834"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Java data grid library","requires_auth":"low_privilege","summary":"Attackers can read sensitive configuration details or credentials from application logs when using JGroups with JDBC_PING in Infinispan.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"A flaw was found in Infinispan, when using JGroups with JDBC_PING. This issue occurs when an application inadvertently exposes sensitive information, such as configuration details or credentials, through logging mechanisms. This exposure can lead to unauthorized access and exploitation by malicious actors.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Org.infinispan-infinispan-parent: exposure of sensitive information in application logs","id":"CVE-2025-0736","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Improper Access Control vulnerability in EmbedAI","id":"CVE-2025-0739"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["15.1.4.Final"],"package":"org.infinispan:infinispan-parent","purl":null,"source":"GHSA-269m-c36j-r834"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["15.1.4.Final"],"package":"org.infinispan:infinispan-parent","purl":"pkg:maven/org.infinispan/infinispan-parent","source":"GHSA-269m-c36j-r834"}],"prev":{"headline":"y_project RuoYi Whitelist getBeanName deserialization","id":"CVE-2025-0734"},"products":["Red Hat Data Grid"],"published":"2025-01-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-11","vendors":["Red Hat"]},"summary":"Attackers can read sensitive configuration details or credentials from application logs when using JGroups with JDBC_PING in Infinispan.","url":"https://insights.sbomify.com/CVE-2025-0736/"}