{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67278 exists.","fix":"No fix has been published for CVE-2026-67278 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67278 is a medium-severity vulnerability in Mikrotik Routeros, published on 5 Sep 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-67278 and fix it if it is affected.\n\nWhat it is: CVE-2026-67278 is a medium-severity vulnerability in Mikrotik Routeros, published on 5 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67278 exists.\n\nAffected product: Mikrotik Routeros. 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-67278/ (Markdown: https://insights.sbomify.com/CVE-2026-67278/index.md)","id":"CVE-2026-67278","markdown":"https://insights.sbomify.com/CVE-2026-67278/index.md","name":"CVE-2026-67278","record":{"aliases":["GHSA-cq44-x9vf-fpqg"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MikroTik RouterOS","requires_auth":"none","summary":"Attackers can impersonate TLS servers and bypass SSH authentication by exploiting flawed RSA signature validation in MikroTik RouterOS.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[{"product":"routeros","vendor":"mikrotik"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"MikroTik RouterOS accepts malformed RSA/PKCS#1 v1.5 signatures across RSA-based services, including TLS/X.509 certificate validation and SSH host-key authentication. Because its trust store includes an e=3 root CA, an attacker controlling or redirecting an outbound RouterOS TLS connection can use the root’s public certificate - without its private key - to forge a trusted intermediate and issue certificates for arbitrary hostnames, enabling TLS server impersonation. The same permissive verification also undermines RSA-based SSH authentication.\n\nThis issue affects only 7.x branch was fixed in versions: 7.23.6 (Long-term) and 7.24.3 (Stable).\nReleases 7.23.4 and 7.24.2 included an incomplete fix.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"TLS server impersonation possible in Mikrotik RouterOS","id":"CVE-2026-67278","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mikrotik:routeros","products":["mikrotik:routeros"],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Mikrotik RouterOS Improper Enforcement of Behavioral Workflow","id":"CVE-2026-67279"},"packages":[],"prev":{"headline":"MikroTik RouterOS Missing Authentication for Critical Function","id":"CVE-2026-67277"},"products":["RouterOS"],"published":"2026-09-05","related":[{"cvss_score":9.8,"headline":"MikroTik RouterOS Stack-Based Buffer Overflow","id":"CVE-2018-7445","kev_date_added":"2022-09-08","published":"2018-03-19"},{"cvss_score":9.2,"headline":"MikroTik RouterOS Improper Neutralization of Argument Delimiters in a Command","id":"CVE-2026-86060","kev_date_added":"2026-09-10","published":"2026-09-05"},{"cvss_score":9.1,"headline":"MikroTik Router OS Directory Traversal","id":"CVE-2018-14847","kev_date_added":"2021-12-01","published":"2018-08-02"},{"cvss_score":8.8,"headline":"MikroTik RouterOS Missing Authentication for Critical Function","id":"CVE-2026-67277","kev_date_added":"2026-09-10","published":"2026-09-05"},{"cvss_score":6.9,"headline":"Mikrotik RouterOS Improper Enforcement of Behavioral Workflow","id":"CVE-2026-67279","kev_date_added":"2026-09-25","published":"2026-09-05"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-20149","kev_date_added":null,"published":"2022-10-15"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2022-34960","kev_date_added":null,"published":"2022-08-25"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["Mikrotik"]},"summary":"Attackers can impersonate TLS servers and bypass SSH authentication by exploiting flawed RSA signature validation in MikroTik RouterOS.","url":"https://insights.sbomify.com/CVE-2026-67278/"}