{"id":"CVE-2026-100676","title":"January, the media proxy/embed service of stoatchat (stoatchat/stoatchat), before version 0.15.5 improperly resolves SVG <image href> values as local filesystem paths when a fetched resource is served as image/svg+xml","summary":"January, the media proxy/embed service of stoatchat (stoatchat/stoatchat), before version 0.15.5 improperly resolves SVG <image href> values as local filesystem paths when a fetched resource is served as image/svg+xml. An unauthenticated…","severity":"high","cvss":8.2,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H","cwe":["CWE-693"],"vendor":"stoatchat","product":"stoatchat","affected":["stoatchat < 0.15.5"],"published":"2026-09-26","updated":"2026-09-28","sourceUpdated":"2026-09-28T17:17:44.810","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-100676","references":[{"url":"https://github.com/stoatchat/stoatchat/security/advisories/GHSA-qv38-hwhv-jm49","label":"disclosure@vulncheck.com"},{"url":"https://www.vulncheck.com/advisories/stoatchat-before-0.15.5-local-filesystem-read-via-svg","label":"disclosure@vulncheck.com"},{"url":"https://github.com/stoatchat/stoatchat/security/advisories/GHSA-qv38-hwhv-jm49","label":"134c704f-9b21-4f2e-91b3-4a467353bcc0"}],"tags":["nvd","cve.org","exploit-available"],"exploitAvailable":true,"ssvc":{"exploitation":"poc","automatable":"yes","technicalImpact":"partial","timestamp":"2026-09-28T16:32:41.399938Z"},"ingestedAt":"2026-09-26T13:33:20.910Z","epss":0.00505,"epssPercentile":0.42934,"slug":"CVE-2026-100676","body":"## Overview\n\nJanuary, the media proxy/embed service of stoatchat (stoatchat/stoatchat), before version 0.15.5 improperly resolves SVG <image href> values as local filesystem paths when a fetched resource is served as image/svg+xml. An unauthenticated remote attacker who causes the service to proxy an attacker-hosted SVG (e.g. via the /proxy endpoint) can determine whether local files exist through observable response-time differences, and can cause supported local image files to be disclosed after re-encoding. Because each referenced file is read in full with no effective limit on the number or total volume of reads, a single request can also generate an unbounded amount of local filesystem I/O and memory pressure (the published proof of concept drives about 4.34 GB of reads), leading to denial of service. The issue is fixed in 0.15.5.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"midnight","depthScore":57,"depthScoreParts":{"impact":45.1,"likelihood":0.1,"exploitation":12,"ransomware":0},"changes":[{"seq":212030,"id":"CVE-2026-100676","ts":1790615834006,"field":"exploit_available","old":"false","new":"true"}]}