{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-12886 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-12886 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-12886 is a high-severity vulnerability in n/a, published on 22 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-12886 and fix it if it is affected.\n\nWhat it is: CVE-2018-12886 is a high-severity vulnerability in n/a, published on 22 May 2019. 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-2018-12886 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2018-12886/ (Markdown: https://insights.sbomify.com/CVE-2018-12886/index.md)","id":"CVE-2018-12886","markdown":"https://insights.sbomify.com/CVE-2018-12886/index.md","name":"CVE-2018-12886","record":{"aliases":["GHSA-5mwp-7q9c-cgg2","UBUNTU-CVE-2018-12886"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"GCC compiler","requires_auth":"none","summary":"GCC compiler flaw allows attackers to bypass stack protector mitigations on ARM targets by controlling the stack canary comparison value.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gcc","vendor":"gnu"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"stack_protect_prologue in cfgexpand.c and stack_protect_epilogue in function.c in GNU Compiler Collection (GCC) 4.1 through 8 (under certain circumstances) generate instruction sequences when targeting ARM targets that spill the address of the stack protector guard, which allows an attacker to bypass the protection of -fstack-protector, -fstack-protector-all, -fstack-protector-strong, and -fstack-protector-explicit against stack overflow by controlling what the stack canary is compared against.","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":"Security feature bypass in n/a","id":"CVE-2018-12886","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-12889"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2018-12885"},"products":["n/a"],"published":"2019-05-22","related":[{"cvss_score":7.8,"headline":"Integer overflow in the new[] operator in gcc before 4.8.0 allows attackers to have unspecified impacts.","id":"CVE-2002-2439","kev_date_added":null,"published":"2019-10-23"},{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2019-15847","kev_date_added":null,"published":"2019-09-02"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2008-1367","kev_date_added":null,"published":"2008-03-17"},{"cvss_score":6.8,"headline":"Integer overflow in n/a","id":"CVE-2008-1685","kev_date_added":null,"published":"2008-04-06"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2021-46195","kev_date_added":null,"published":"2022-01-14"},{"cvss_score":5,"headline":"Weak cryptography in n/a","id":"CVE-2015-5276","kev_date_added":null,"published":"2015-11-17"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-14","vendors":["n/a"]},"summary":"GCC compiler flaw allows attackers to bypass stack protector mitigations on ARM targets by controlling the stack canary comparison value.","url":"https://insights.sbomify.com/CVE-2018-12886/"}