{"answers":{"affected":"It affects 26 products.","exploited":"There is no known exploitation of CVE-2023-26069 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-26069 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-26069 is a critical vulnerability in n/a, published on 10 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-26069 and fix it if it is affected.\n\nWhat it is: CVE-2023-26069 is a critical vulnerability in n/a, published on 10 Apr 2023. 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-2023-26069 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2023-26069/ (Markdown: https://insights.sbomify.com/CVE-2023-26069/index.md)","id":"CVE-2023-26069","markdown":"https://insights.sbomify.com/CVE-2023-26069/index.md","name":"CVE-2023-26069","record":{"aliases":["GHSA-gcx9-562f-5mwm"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Lexmark printer","requires_auth":"none","summary":"Lexmark devices mishandle input validation, potentially allowing attackers to exploit unspecified weaknesses in device processing.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cslbl_firmware","vendor":"lexmark"},{"product":"cslbn_firmware","vendor":"lexmark"},{"product":"csnzj_firmware","vendor":"lexmark"},{"product":"cstat_firmware","vendor":"lexmark"},{"product":"cstmh_firmware","vendor":"lexmark"},{"product":"cstpc_firmware","vendor":"lexmark"},{"product":"cxlbl_firmware","vendor":"lexmark"},{"product":"cxlbn_firmware","vendor":"lexmark"},{"product":"cxnzj_firmware","vendor":"lexmark"},{"product":"cxtat_firmware","vendor":"lexmark"},{"product":"cxtmm_firmware","vendor":"lexmark"},{"product":"cxtpc_firmware","vendor":"lexmark"},{"product":"cxtpp_firmware","vendor":"lexmark"},{"product":"cxtzj_firmware","vendor":"lexmark"},{"product":"mslbd_firmware","vendor":"lexmark"},{"product":"mslsg_firmware","vendor":"lexmark"},{"product":"msngm_firmware","vendor":"lexmark"},{"product":"msngw_firmware","vendor":"lexmark"},{"product":"mstgw_firmware","vendor":"lexmark"},{"product":"mxlbd_firmware","vendor":"lexmark"},{"product":"mxlsg_firmware","vendor":"lexmark"},{"product":"mxngm_firmware","vendor":"lexmark"},{"product":"mxtct_firmware","vendor":"lexmark"},{"product":"mxtgm_firmware","vendor":"lexmark"},{"product":"mxtgw_firmware","vendor":"lexmark"},{"product":"mxtpm_firmware","vendor":"lexmark"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Certain Lexmark devices through 2023-02-19 mishandle Input Validation (issue 3 of 4).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2023-26069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2023-26070"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2023-26068"},"products":["n/a"],"published":"2023-04-10","related":[{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2023-26063","kev_date_added":null,"published":"2023-04-10"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-26064","kev_date_added":null,"published":"2023-04-10"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2023-26065","kev_date_added":null,"published":"2023-04-10"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2023-26066","kev_date_added":null,"published":"2023-04-10"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2023-26068","kev_date_added":null,"published":"2023-04-10"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2023-26070","kev_date_added":null,"published":"2023-04-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2025-02-11","vendors":["n/a"]},"summary":"Lexmark devices mishandle input validation, potentially allowing attackers to exploit unspecified weaknesses in device processing.","url":"https://insights.sbomify.com/CVE-2023-26069/"}