{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41329 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41329 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41329 is a medium-severity vulnerability in n/a, published on 27 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41329 and fix it if it is affected.\n\nWhat it is: CVE-2021-41329 is a medium-severity vulnerability in n/a, published on 27 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-41329 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-2021-41329/ (Markdown: https://insights.sbomify.com/CVE-2021-41329/index.md)","id":"CVE-2021-41329","markdown":"https://insights.sbomify.com/CVE-2021-41329/index.md","name":"CVE-2021-41329","record":{"aliases":["GHSA-59vg-279r-wf25"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Seq log server","requires_auth":"low_privilege","summary":"Attackers can view unauthorized log data due to cache key collisions when using specific query filters in Seq.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"seq","vendor":"datalust"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-682","name":"Incorrect Calculation"}],"description":"Datalust Seq before 2021.2.6259 allows users (with view filters applied to their accounts) to see query results not constrained by their view filter. This information exposure, caused by an internal cache key collision, occurs when the user's view filter includes an array or IN clause, and when another user has recently executed an identical query differing only by the array elements.","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":"Information disclosure in n/a","id":"CVE-2021-41329","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Microsoft Windows Media Foundation Remote Code Execution Vulnerability","id":"CVE-2021-41330"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2021-41326"},"products":["n/a"],"published":"2021-09-27","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2018-8096","kev_date_added":null,"published":"2018-03-14"},{"cvss_score":9.1,"headline":"Privilege escalation in n/a","id":"CVE-2024-29866","kev_date_added":null,"published":"2024-03-21"},{"cvss_score":8.8,"headline":"Cross-site request forgery in Seq","id":"CVE-2025-27912","kev_date_added":null,"published":"2025-03-11"},{"cvss_score":6.5,"headline":"Denial of service in Seq","id":"CVE-2025-27911","kev_date_added":null,"published":"2025-03-11"},{"cvss_score":5.7,"headline":"Denial of service in Seq","id":"CVE-2024-58102","kev_date_added":null,"published":"2025-03-11"},{"cvss_score":4.9,"headline":"Information disclosure in n/a","id":"CVE-2023-38195","kev_date_added":null,"published":"2023-07-22"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can view unauthorized log data due to cache key collisions when using specific query filters in Seq.","url":"https://insights.sbomify.com/CVE-2021-41329/"}