{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.logging.log4j:log4j-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-68161 in the wild and no public exploit code.","fix":"Upgrade org.apache.logging.log4j:log4j-core to 2.25.3 or later.","what":"CVE-2025-68161 is a medium-severity vulnerability in Apache Log4j Core, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68161 and fix it if it is affected.\n\nWhat it is: CVE-2025-68161 is a medium-severity vulnerability in Apache Log4j Core, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68161 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.logging.log4j:log4j-core (Maven): affected from 2.0-beta9; fixed in 2.25.3\n- org.apache.logging.log4j:log4j-core (Maven): affected from 2.0-beta9; fixed in 2.25.3\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-68161/ (Markdown: https://insights.sbomify.com/CVE-2025-68161/index.md)","id":"CVE-2025-68161","markdown":"https://insights.sbomify.com/CVE-2025-68161/index.md","name":"CVE-2025-68161","record":{"aliases":["CLEANSTART-2026-AT67837","CLEANSTART-2026-FS24569","CLEANSTART-2026-MW42084","CLEANSTART-2026-NM32016","CLSA-2026-1779842948","CLSA-2026-1781052749","CLSA-2026-1791900475","DEBIAN-CVE-2025-68161","DLA-4444-1","ECHO-6f17-219d-b8c8","GHSA-vc5p-v9hr-52mj","MINI-2443-w96w-fwhx","MINI-257v-rc7m-mjvh","MINI-3382-c7h2-5hj3","MINI-35jg-9338-87mm","MINI-3934-3w2w-6cfc","MINI-42jf-8j3j-qg86","MINI-46wc-cfgp-qqwf","MINI-47xf-88p9-rv37","MINI-4946-h5h9-rrx3","MINI-49wv-3prw-jvfp","MINI-4mwj-5vm9-23wp","MINI-55w5-2mgq-vq42","MINI-5c46-x8mj-v26p","MINI-5v59-79f7-5f98","MINI-62j8-pw3f-4h5m","MINI-6h82-99jm-7x84","MINI-775f-6qxw-3jr5","MINI-79r5-h9qh-mxqq","MINI-7jvf-xwhp-gr7r","MINI-83pg-p8xh-xjpr","MINI-877c-pvvh-p72v","MINI-89f3-gvcw-538f","MINI-8c3j-9894-wm98","MINI-8wr5-h6mw-pcpg","MINI-99hm-5rrh-9rq5","MINI-9m73-xq46-44jx","MINI-9mcj-8rvr-6fh8","MINI-9vmq-r48g-j67m","MINI-cj36-p2gf-8m9w","MINI-cxxx-q5jg-hxc8","MINI-fcrm-8prh-rhpf","MINI-fgjv-mp25-mr6j","MINI-fxc8-r6hh-w8cf","MINI-g325-hmrc-mmc6","MINI-g7wg-ppqv-4pf3","MINI-gc2f-f7jj-2xqj","MINI-gpf7-mq98-x554","MINI-gpgg-w882-vvv2","MINI-h4r6-3wrj-9v8g","MINI-h683-cv4m-8hw3","MINI-h9w4-vrr5-5h43","MINI-hg59-prjf-34wj","MINI-hpp3-9ccv-ff4x","MINI-hx2p-jh4v-hchf","MINI-j4c7-pj6m-mmh6","MINI-j4gp-xxxv-jpfm","MINI-j6cp-9chv-px8g","MINI-j85p-6447-mh3w","MINI-jqjp-rjq5-pjvq","MINI-jx37-v9r6-x3fm","MINI-m2vw-v877-66c9","MINI-m946-9q8h-c4vx","MINI-mxr8-4gvr-24rv","MINI-pg6m-v2mp-w444","MINI-pmxq-2cq4-qmj3","MINI-prw4-grpr-qhv3","MINI-q777-6gfg-cvx3","MINI-qx6m-rwrf-h6x7","MINI-r3x4-6h9f-gccq","MINI-r4h5-r9f2-2mvq","MINI-rg6p-3pc8-8fq6","MINI-rppv-x7qw-7v4w","MINI-v8vm-6p23-4776","MINI-vqgq-rc86-58hm","MINI-w4f3-mv92-p4xw","MINI-wmwg-wxpj-8jxw","MINI-wv48-3xr3-5f4g","MINI-xc5h-g92f-527h","MINI-xr6x-v28h-8fj5","ROOT-APP-MAVEN-CVE-2025-68161","SUSE-SU-2026:0254-1","UBUNTU-CVE-2025-68161","openSUSE-SU-2026:10009-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Java logging library","requires_auth":"none","summary":"Man-in-the-middle attackers can intercept or redirect log traffic due to missing TLS hostname verification in the Socket Appender.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"log4j","vendor":"apache"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"},{"id":"CWE-297","name":"Improper Validation of Certificate with Host Mismatch"}],"description":"The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\n\nThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\n\n  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\n  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\n\nUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\n\nAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.","ecosystems":["Maven","SUSE:Linux Enterprise Module for Basesystem 15 SP7","openSUSE:Leap 15.6","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Apache Log4j Core: Missing TLS hostname verification in Socket appender","id":"CVE-2025-68161","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":5,"n_references":6,"next":{"headline":"Code injection in TeamCity","id":"CVE-2025-68162"},"packages":[{"ecosystem":"Maven","fixed":["2.25.3"],"introduced":["2.0-beta9"],"last_affected":[],"package":"org.apache.logging.log4j:log4j-core","purl":null,"source":"GHSA-vc5p-v9hr-52mj"},{"ecosystem":"Maven","fixed":["2.25.3"],"introduced":["2.0-beta9"],"last_affected":[],"package":"org.apache.logging.log4j:log4j-core","purl":"pkg:maven/org.apache.logging.log4j/log4j-core","source":"GHSA-vc5p-v9hr-52mj"},{"ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","fixed":["2.20.0-150200.4.30.1"],"introduced":["0"],"last_affected":[],"package":"log4j","purl":"pkg:rpm/suse/log4j\u0026distro=SUSE%20Linux%20Enterprise%20Module%20for%20Basesystem%2015%20SP7","source":"SUSE-SU-2026:0254-1"},{"ecosystem":"openSUSE:Leap 15.6","fixed":["2.20.0-150200.4.30.1"],"introduced":["0"],"last_affected":[],"package":"log4j","purl":"pkg:rpm/opensuse/log4j\u0026distro=openSUSE%20Leap%2015.6","source":"SUSE-SU-2026:0254-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["2.20.0-1.1"],"introduced":["0"],"last_affected":[],"package":"log4j","purl":"pkg:rpm/opensuse/log4j\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:10009-1"}],"prev":{"headline":"Heap out-of-bounds write in BIO_f_linebuffer on short writes","id":"CVE-2025-68160"},"products":["Apache Log4j Core"],"published":"2025-12-18","related":[{"cvss_score":10,"headline":"Apache Log4j2 Remote Code Execution","id":"CVE-2021-44228","kev_date_added":"2021-12-10","published":"2021-12-10"},{"cvss_score":9,"headline":"Apache Log4j2 Deserialization of Untrusted Data","id":"CVE-2021-45046","kev_date_added":"2023-05-01","published":"2021-12-14"},{"cvss_score":9.8,"headline":"SQL injection in JDBC Appender in Apache Log4j V1","id":"CVE-2022-23305","kev_date_added":null,"published":"2022-01-18"},{"cvss_score":9.8,"headline":"Deserialization of Untrusted Data in Log4j","id":"CVE-2017-5645","kev_date_added":null,"published":"2017-04-17"},{"cvss_score":8.8,"headline":"Deserialization of untrusted data in JMSSink in Apache Log4j 1.x","id":"CVE-2022-23302","kev_date_added":null,"published":"2022-01-18"},{"cvss_score":7.5,"headline":"Apache Log4j 1.x (EOL) allows DoS in Chainsaw and SocketAppender","id":"CVE-2023-26464","kev_date_added":null,"published":"2023-03-10"},{"cvss_score":7.5,"headline":"Deserialization of untrusted data in JMSAppender in Apache Log4j 1.2","id":"CVE-2021-4104","kev_date_added":null,"published":"2021-12-14"}],"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":"CC BY 4.0","name":"SUSE","prefix":"SUSE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"2026-04-10","vendors":["Apache Software Foundation"]},"summary":"Man-in-the-middle attackers can intercept or redirect log traffic due to missing TLS hostname verification in the Socket Appender.","url":"https://insights.sbomify.com/CVE-2025-68161/"}