{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-29779 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-29779 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-29779 is a high-severity vulnerability in lyc8503 UptimeFlare, published on 7 Mar 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-29779 and fix it if it is affected.\n\nWhat it is: CVE-2026-29779 is a high-severity vulnerability in lyc8503 UptimeFlare, published on 7 Mar 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-29779 in the wild and no public exploit code.\n\nAffected product: lyc8503 UptimeFlare. 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-29779/ (Markdown: https://insights.sbomify.com/CVE-2026-29779/index.md)","id":"CVE-2026-29779","markdown":"https://insights.sbomify.com/CVE-2026-29779/index.md","name":"CVE-2026-29779","record":{"aliases":["GHSA-36q9-v7p3-vj6v"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Uptime monitoring service","requires_auth":"none","summary":"Attackers can view sensitive server-side configuration and credentials by inspecting the client-side JavaScript bundle of the UptimeFlare status page.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"uptimeflare","vendor":"lyc8503"}],"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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"UptimeFlare is a serverless uptime monitoring \u0026 status page solution, powered by Cloudflare Workers. Prior to commit 377a596, configuration file uptime.config.ts exports both pageConfig (safe for client use) and workerConfig (server-only, contains sensitive data) from the same module. Due to pages/incidents.tsx importing and using workerConfig directly inside client-side component code, the entire workerConfig object was included in the client-side JavaScript bundle served to all visitors. This issue has been patched via commit 377a596.","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":"UptimeFlare: Montior config / Credentials in `workerConfig` exposed in client-side JavaScript bundle","id":"CVE-2026-29779","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":"eml_parser: Path Traversal in Official Example Script Leading to Arbitrary File Write","id":"CVE-2026-29780"},"packages":[],"prev":{"headline":"pyLoad: Arbitrary File Write via Path Traversal in edit_package()","id":"CVE-2026-29778"},"products":["UptimeFlare"],"published":"2026-03-07","related":[],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-09","vendors":["lyc8503"]},"summary":"Attackers can view sensitive server-side configuration and credentials by inspecting the client-side JavaScript bundle of the UptimeFlare status page.","url":"https://insights.sbomify.com/CVE-2026-29779/"}