{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-71862 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-71862 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-71862 is a high-severity vulnerability in bluewave-labs Checkmate, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-71862 and fix it if it is affected.\n\nWhat it is: CVE-2026-71862 is a high-severity vulnerability in bluewave-labs Checkmate, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-71862 in the wild and no public exploit code.\n\nAffected product: bluewave-labs Checkmate. 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-71862/ (Markdown: https://insights.sbomify.com/CVE-2026-71862/index.md)","id":"CVE-2026-71862","markdown":"https://insights.sbomify.com/CVE-2026-71862/index.md","name":"CVE-2026-71862","record":{"aliases":["GHSA-3m74-8cg9-rp8j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Server monitoring tool","requires_auth":"none","summary":"Enabling the showURL setting exposes sensitive bearer tokens in API responses, allowing attackers to steal credentials for monitored services.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Checkmate is an open-source, self-hosted tool designed to track and monitor server hardware, uptime, response times, and incidents in real-time with beautiful visualizations. From 3.3.0 until 3.9.2, enabling the global showURL setting causes the unauthenticated GET /api/v1/status-page/:url endpoint to return complete monitor objects from server/src/controllers/statusPageController.ts. The response includes the secret field used by HttpProvider.ts as an HTTP Authorization credential, even though BaseStatusPage.tsx does not display that value, allowing visitors to extract credentials from the JSON response and use them against monitored services. This issue is fixed in version 3.9.2.","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":"Checkmate: Sensitive Bearer Token Exposure via Public Status Pages When showURL Setting is Enabled","id":"CVE-2026-71862","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Orval: Import-time RCE via header parameter name -\u003e computed-property-key injection in the zod client","id":"CVE-2026-71864"},"packages":[],"prev":{"headline":"Notepad++: shortcuts.xml Macro HMAC Bypass Enables Conditional Elevated Command Execution","id":"CVE-2026-71858"},"products":["Checkmate"],"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-21","vendors":["bluewave-labs"]},"summary":"Enabling the showURL setting exposes sensitive bearer tokens in API responses, allowing attackers to steal credentials for monitored services.","url":"https://insights.sbomify.com/CVE-2026-71862/"}