{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103097 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103097 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103097 is a high-severity vulnerability in GeoVision Inc. GV-Eye, published on 2 Oct 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-103097 and fix it if it is affected.\n\nWhat it is: CVE-2026-103097 is a high-severity vulnerability in GeoVision Inc. GV-Eye, published on 2 Oct 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-103097 in the wild and no public exploit code.\n\nAffected product: GeoVision Inc. GV-Eye. 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-103097/ (Markdown: https://insights.sbomify.com/CVE-2026-103097/index.md)","id":"CVE-2026-103097","markdown":"https://insights.sbomify.com/CVE-2026-103097/index.md","name":"CVE-2026-103097","record":{"aliases":["GHSA-mwfx-8rgq-rc8f"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"GV-Eye mobile app","requires_auth":"none","summary":"Attackers can extract hardcoded API keys from the GV-Eye Android application to access payment services and bypass security controls.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GV","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-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-540","name":"Inclusion of Sensitive Information in Source Code"},{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"An API key is\nhardcoded and retrievable from the application package. Since Android\napplications can be reverse engineered, embedding sensitive API credentials\ndirectly in the client application may allow unauthorized users to extract and\nmisuse the key.","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":"GV-Eye Relay Payment API Key Vulnerability","id":"CVE-2026-103097","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"GV-Eye Sensitive information exposure in URL query parameter Vulnerability","id":"CVE-2026-103098"},"packages":[],"prev":{"headline":"GV-Eye Hardcoded API Key Vulnerability","id":"CVE-2026-103096"},"products":["GV-Eye"],"published":"2026-10-02","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-10-02","vendors":["GeoVision Inc."]},"summary":"Attackers can extract hardcoded API keys from the GV-Eye Android application to access payment services and bypass security controls.","url":"https://insights.sbomify.com/CVE-2026-103097/"}