{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-26208 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2020-26208 is a medium-severity memory corruption vulnerability in n/a, published on 2 Feb 2022. 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-2020-26208 and fix it if it is affected.\n\nWhat it is: CVE-2020-26208 is a medium-severity memory corruption vulnerability in n/a, published on 2 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-26208 exists.\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-2020-26208/ (Markdown: https://insights.sbomify.com/CVE-2020-26208/index.md)","id":"CVE-2020-26208","markdown":"https://insights.sbomify.com/CVE-2020-26208/index.md","name":"CVE-2020-26208","record":{"aliases":["DEBIAN-CVE-2020-26208","GHSA-7pr6-xq4f-qhgc","UBUNTU-CVE-2020-26208"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Jhead EXIF tool","requires_auth":"low_privilege","summary":"A heap-buffer-overflow in Jhead allows attackers to cause crashes or potentially execute code via crafted JPEG images.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jhead","vendor":"jhead_project"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"JHEAD is a simple command line tool for displaying and some manipulation of EXIF header data embedded in Jpeg images from digital cameras. In affected versions there is a heap-buffer-overflow on jhead-3.04/jpgfile.c:285 ReadJpegSections. Crafted jpeg images can be provided to the user resulting in a program crash or potentially incorrect exif information retrieval. Users are advised to upgrade. There is no known workaround for this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Heap-buffer-overflow in jhead","id":"CVE-2020-26208","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-Site Scripting in BookStack","id":"CVE-2020-26210"},"packages":[],"prev":{"headline":"Unsafe deserialization in DatabaseSchemaViewer","id":"CVE-2020-26207"},"products":["n/a"],"published":"2022-02-02","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-28550","kev_date_added":null,"published":"2023-06-13"},{"cvss_score":7.8,"headline":"Use after free in n/a","id":"CVE-2025-44906","kev_date_added":null,"published":"2025-05-30"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-28277","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-28278","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":7.8,"headline":"Memory corruption in jhead","id":"CVE-2021-3496","kev_date_added":null,"published":"2021-04-22"},{"cvss_score":7.8,"headline":"Other in n/a","id":"CVE-2018-16554","kev_date_added":null,"published":"2018-09-16"},{"cvss_score":7.8,"headline":"Integer overflow in n/a","id":"CVE-2018-17088","kev_date_added":null,"published":"2018-09-16"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-05","vendors":["n/a"]},"summary":"A heap-buffer-overflow in Jhead allows attackers to cause crashes or potentially execute code via crafted JPEG images.","url":"https://insights.sbomify.com/CVE-2020-26208/"}