{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3283 exists.","fix":"Apply the vendor's patch.","what":"CVE-2026-3283 is a medium-severity memory corruption vulnerability in libvips, published on 27 Feb 2026. 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-2026-3283 and fix it if it is affected.\n\nWhat it is: CVE-2026-3283 is a medium-severity memory corruption vulnerability in libvips, published on 27 Feb 2026. 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-2026-3283 exists.\n\nAffected product: libvips. 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-2026-3283/ (Markdown: https://insights.sbomify.com/CVE-2026-3283/index.md)","id":"CVE-2026-3283","markdown":"https://insights.sbomify.com/CVE-2026-3283/index.md","name":"CVE-2026-3283","record":{"aliases":["DEBIAN-CVE-2026-3283","GHSA-93j6-h3cr-cp28","UBUNTU-CVE-2026-3283"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Image processing library","requires_auth":"low_privilege","summary":"A local attacker can trigger an out-of-bounds read in libvips, potentially causing a crash or leaking sensitive memory contents.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"libvips","vendor":"libvips"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A vulnerability has been found in libvips 8.19.0. This issue affects the function vips_extract_band_build of the file libvips/conversion/extract.c. The manipulation of the argument extract_band leads to out-of-bounds read. The attack needs to be performed locally. The exploit has been disclosed to the public and may be used. The identifier of the patch is 24795bb3d19d84f7b6f5ed86451ad556c8f2fe70. To fix this issue, it is recommended to deploy a patch.","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":"libvips extract.c vips_extract_band_build out-of-bounds","id":"CVE-2026-3283","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"libvips extract.c vips_extract_area_build integer overflow","id":"CVE-2026-3284"},"packages":[],"prev":{"headline":"libvips unpremultiply.c vips_unpremultiply_build out-of-bounds","id":"CVE-2026-3282"},"products":["libvips"],"published":"2026-02-27","related":[{"cvss_score":8.8,"headline":"Use after free in n/a","id":"CVE-2019-17534","kev_date_added":null,"published":"2019-10-13"},{"cvss_score":7,"headline":"Possible integer overflow leading to potential heap-based buffer overflow","id":"CVE-2026-33327","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":7,"headline":"Possible heap-based buffer overflow when decoding TIFF image containing well-crafted tile","id":"CVE-2026-35591","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":6.8,"headline":"Possible integer overflow on 32-bit systems when reading GIF images","id":"CVE-2026-33328","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":6.8,"headline":"Possible out-of-bounds read leading to crash when decoding well-crafted EXIF metadata","id":"CVE-2026-35590","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2021-27847","kev_date_added":null,"published":"2021-07-15"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2019-6976","kev_date_added":null,"published":"2019-01-26"}],"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":"2026-02-27","vendors":["n/a"]},"summary":"A local attacker can trigger an out-of-bounds read in libvips, potentially causing a crash or leaking sensitive memory contents.","url":"https://insights.sbomify.com/CVE-2026-3283/"}