{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27694 exists.","fix":"No fix has been published for CVE-2026-27694 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27694 is a medium-severity cross-site scripting vulnerability in traccar, published on 5 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-27694 and fix it if it is affected.\n\nWhat it is: CVE-2026-27694 is a medium-severity cross-site scripting vulnerability in traccar, published on 5 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27694 exists.\n\nAffected product: traccar. 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-27694/ (Markdown: https://insights.sbomify.com/CVE-2026-27694/index.md)","id":"CVE-2026-27694","markdown":"https://insights.sbomify.com/CVE-2026-27694/index.md","name":"CVE-2026-27694","record":{"aliases":["GHSA-6hfr-mj4m-hrvv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":false,"product_category":"GPS tracking system","requires_auth":"low_privilege","summary":"Attackers can inject HTML into notification emails via device names, enabling phishing or spoofing against other users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"traccar","vendor":"traccar"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Traccar is an open source GPS tracking system. In org.traccar:traccar versions starting at 6.11.1 before 6.13.0, the email notification templates insert user-controlled device, geofence, and driver names into HTML email output without proper escaping. An attacker with low privileges can store crafted HTML in these fields, which is then rendered in notification emails sent to other users with access to the affected devices. This can lead to phishing or spoofed email content. This issue is fixed in version 6.13.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"traccar allows stored HTML injection in notification emails","id":"CVE-2026-27694","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"zae-limiter: DynamoDB hot partition throttling enables per-entity Denial of Service","id":"CVE-2026-27695"},"packages":[],"prev":{"headline":"traccar allows XML injection in KML and GPX exports","id":"CVE-2026-27693"},"products":["traccar"],"published":"2026-05-05","related":[{"cvss_score":9.7,"headline":"Traccar's unrestricted file upload vulnerability in device image upload could lead to remote code execution","id":"CVE-2024-31214","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":9.5,"headline":"Use of default credentials at Traccar fleet management solution","id":"CVE-2024-7746","kev_date_added":null,"published":"2024-08-13"},{"cvss_score":8.7,"headline":"Traccar Vulnerable to Stored Cross-Site Scripting (XSS) via Malicious SVG File Upload","id":"CVE-2026-25648","kev_date_added":null,"published":"2026-02-23"},{"cvss_score":8.5,"headline":"An unrestricted file upload vulnerability in traccar leads to RCE","id":"CVE-2023-50729","kev_date_added":null,"published":"2024-01-15"},{"cvss_score":7.7,"headline":"LDAP injection vulnerability in Traccar GPS Tracking System","id":"CVE-2020-5246","kev_date_added":null,"published":"2020-07-14"},{"cvss_score":7.3,"headline":"Traccar Vulnerable to Authorization Code Theft via Open Redirect in OIDC Provider Endpoints","id":"CVE-2026-25649","kev_date_added":null,"published":"2026-02-23"},{"cvss_score":7.1,"headline":"Traccar Missing Origin Validation in WebSockets","id":"CVE-2025-68930","kev_date_added":null,"published":"2026-02-23"}],"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-05-05","vendors":["traccar"]},"summary":"Attackers can inject HTML into notification emails via device names, enabling phishing or spoofing against other users.","url":"https://insights.sbomify.com/CVE-2026-27694/"}