{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-48106 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-48106 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-48106 is a high-severity missing authorization vulnerability in Basekick-Labs arc, published on 21 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-48106 and fix it if it is affected.\n\nWhat it is: CVE-2026-48106 is a high-severity missing authorization vulnerability in Basekick-Labs arc, published on 21 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-48106 in the wild and no public exploit code.\n\nAffected product: Basekick-Labs arc. 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-48106/ (Markdown: https://insights.sbomify.com/CVE-2026-48106/index.md)","id":"CVE-2026-48106","markdown":"https://insights.sbomify.com/CVE-2026-48106/index.md","name":"CVE-2026-48106","record":{"aliases":["GHSA-wfgr-8x84-22q7"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Arc time-series database","requires_auth":"low_privilege","summary":"Attackers on the cluster network can inject data into Arc Enterprise databases by sending unauthenticated replication messages, bypassing application-layer security checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-924","name":"Improper Enforcement of Message Integrity During Transmission in a Communication Channel"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Arc is an open, SQL-native time-series database for telemetry. Prior to version 26.06.1, Arc Enterprise's cluster replication receiver at `internal/cluster/replication/receiver.go` validates only the wire-format envelope (length, opcode) of inbound messages. The `MsgReplicateSync` payload itself is accepted without any application-layer authentication — no HMAC, no signature, no per-message nonce. The replication stream is protected at the transport layer by TLS / mTLS, but there is no protection against application-layer message tampering or replay once a peer is on the cluster network. This is fixed in 2026.06.1. Some workarounds are available. Restrict cluster network access to known-trusted peers via strict firewall rules, audit replication logs for unexpected `MsgReplicateSync` traffic, and/or disable cluster mode until the fix is available.","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":"Missing authorization in arc","id":"CVE-2026-48106","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Russh: Unchecked keyboard-interactive prompt count in client auth path","id":"CVE-2026-48107"},"packages":[],"prev":{"headline":"Path traversal in arc","id":"CVE-2026-48105"},"products":["arc"],"published":"2026-08-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["Basekick-Labs"]},"summary":"Attackers on the cluster network can inject data into Arc Enterprise databases by sending unauthenticated replication messages, bypassing application-layer security checks.","url":"https://insights.sbomify.com/CVE-2026-48106/"}