{"answers":{"affected":"1 open source package ship an affected version, including dahl-salso.","exploited":"There is no known exploitation of RUSTSEC-2026-0411 in the wild and no public exploit code.","fix":"Upgrade dahl-salso to 0.7.0 or later.","what":"RUSTSEC-2026-0411 is a vulnerability in dahl-salso, published on 22 Oct 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0411 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0411 is a vulnerability in dahl-salso, published on 22 Oct 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0411 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- dahl-salso (crates.io): affected from 0.0.0-0; fixed in 0.7.0\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/RUSTSEC-2026-0411/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0411/index.md)","id":"RUSTSEC-2026-0411","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0411/index.md","name":"RUSTSEC-2026-0411","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"`Log2Cache::new(n)` fills its three tables with entries for `0..=n`, but the\nthree accessor methods index those tables with `get_unchecked` on a value the\ncaller supplies. Nothing bounds the argument and nothing documents a bound, so\nany value above the `n` the cache was built with reads past the end of the\nvector. `CountType` is `u32`, so the read can land up to `u32::MAX` elements\naway, and `plog2p()` returns the value it read, disclosing whatever lies there.\n\nFor example, `Log2Cache::new(4)` builds tables holding 5 entries (indices\n0,1,2,3,4). Then `cache.nlog2n(60000)` reads index 60000, far outside the\nallocation. Under AddressSanitizer this faults with `SEGV`; Miri reports it as\nundefined behavior at `src/log2cache.rs:42`.\n\n`nlog2n_difference()` is off by one further: in the affected versions `new(n)`\npushes `n` entries into that table rather than `n + 1`, so even\n`nlog2n_difference(n)` is out of bounds.\n\nThis can be triggered through safe public APIs — `Log2Cache::new()` and any of\n`nlog2n()`, `nlog2n_difference()` and `plog2p()` — with no `unsafe` required\nfrom the caller.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Out-of-bounds read in `Log2Cache::nlog2n()`, `nlog2n_difference()` and `plog2p()`","id":"RUSTSEC-2026-0411","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.7.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"dahl-salso","purl":"pkg:cargo/dahl-salso","source":"RUSTSEC-2026-0411"}],"products":null,"published":"2026-10-22","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":null,"url":"https://insights.sbomify.com/RUSTSEC-2026-0411/"}