{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-70634 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-70634 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-70634 is a high-severity vulnerability in timescaledb, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-70634 and fix it if it is affected.\n\nWhat it is: CVE-2026-70634 is a high-severity vulnerability in timescaledb, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-70634 in the wild and no public exploit code.\n\nAffected product: timescaledb. 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-70634/ (Markdown: https://insights.sbomify.com/CVE-2026-70634/index.md)","id":"CVE-2026-70634","markdown":"https://insights.sbomify.com/CVE-2026-70634/index.md","name":"CVE-2026-70634","record":{"aliases":["GHSA-mjw3-r56j-9698"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"TimescaleDB extension","requires_auth":"low_privilege","summary":"Attackers with DML access can trigger an out-of-bounds read in TimescaleDB, disclosing backend memory including shared buffer pool contents.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"timescaledb","vendor":"timescale"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-129","name":"Improper Validation of Array Index"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"TimescaleDB through 2.29.1, fixed in commit 517c13e, contains an out-of-bounds read in the Dictionary compression reverse row iterator (tsl/src/compression/algorithms/dictionary.c). The forward path validates the decoded index; the reverse path uses an assertion compiled out of release builds, leaving the 64-bit Simple8b index unvalidated and the read offset attacker-controlled. Attackers with DML access to a physical compressed relation can store a crafted datum and run a reverse-order scan. With a pass-by-value column type the out-of-bounds Datum is returned to the client as a normal column value, disclosing backend memory including the shared buffer pool, which SQL access control does not cover.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"TimescaleDB 2.29.1 Out-of-Bounds Read Information Disclosure via Dictionary Compression Reverse Iterator","id":"CVE-2026-70634","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"TimescaleDB 2.29.1 Out-of-Bounds Read DoS via Bulk Dictionary Decompression Negative Index","id":"CVE-2026-70635"},"packages":[],"prev":{"headline":"TimescaleDB 2.29.1 Out-of-Bounds Read DoS via Gorilla Compression Reverse Iterator","id":"CVE-2026-70633"},"products":["timescaledb"],"published":"2026-08-06","related":[{"cvss_score":8.8,"headline":"TimescaleDB uses untrusted search path during extension upgrade","id":"CVE-2026-29089","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":8.8,"headline":"TimescaleDB has incorrect access control","id":"CVE-2023-25149","kev_date_added":null,"published":"2023-02-14"},{"cvss_score":8,"headline":"Privilege escalation in n/a","id":"CVE-2022-24128","kev_date_added":null,"published":"2022-03-13"},{"cvss_score":7.1,"headline":"TimescaleDB 2.29.1 Out-of-Bounds Read DoS via Gorilla Compression Reverse Iterator","id":"CVE-2026-70633","kev_date_added":null,"published":"2026-08-06"},{"cvss_score":7.1,"headline":"TimescaleDB 2.29.1 Out-of-Bounds Read DoS via Bulk Dictionary Decompression Negative Index","id":"CVE-2026-70635","kev_date_added":null,"published":"2026-08-06"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["timescale"]},"summary":"Attackers with DML access can trigger an out-of-bounds read in TimescaleDB, disclosing backend memory including shared buffer pool contents.","url":"https://insights.sbomify.com/CVE-2026-70634/"}