{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102371 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-102371 is a medium-severity vulnerability in Canonical Ubuntu Pro for WSL, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102371 and fix it if it is affected.\n\nWhat it is: CVE-2026-102371 is a medium-severity vulnerability in Canonical Ubuntu Pro for WSL, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-102371 in the wild and no public exploit code.\n\nAffected product: Canonical Ubuntu Pro for WSL. 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-102371/ (Markdown: https://insights.sbomify.com/CVE-2026-102371/index.md)","id":"CVE-2026-102371","markdown":"https://insights.sbomify.com/CVE-2026-102371/index.md","name":"CVE-2026-102371","record":{"aliases":["GHSA-j32v-fr72-w8fv","UBUNTU-CVE-2026-102371","USN-8892-1"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ubuntu Pro for WSL","requires_auth":"low_privilege","summary":"An unprivileged local user can read the Ubuntu Pro token from process arguments, allowing unauthorized access to Ubuntu Pro services.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-214","name":"Invocation of Process Using Visible Sensitive Information"}],"description":"In wsl-pro-service before 0.1.19ubuntu3, the service component which runs as root inside each WSL instance attaches the instance to Ubuntu Pro by executing the pro client with the Ubuntu Pro token passed as a command-line argument (pro attach \u003ctoken\u003e). On systems where /proc is mounted without process-hiding mitigations (such as hidepid), which is the default in WSL, an unprivileged local user or process in the same WSL instance can read the token from /proc/\u003cpid\u003e/cmdline while the attach process is running. The leaked token could then be used to attach other machines to the victim's Ubuntu Pro subscription and gain unauthorized access to Ubuntu Pro services.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"wsl-pro-service: Ubuntu Pro token exposed via process command-line arguments","id":"CVE-2026-102371","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":"GestSup before 3.2.61 Stored XSS via Email Body in LOGIN IMAP Connector","id":"CVE-2026-102372"},"packages":[],"prev":{"headline":"Physical UART Access Leading to an Unauthenticated Root Shell in TP-Link Kasa EC70 and EC71","id":"CVE-2026-102370"},"products":["Ubuntu Pro for WSL"],"published":"2026-09-29","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Canonical"]},"summary":"An unprivileged local user can read the Ubuntu Pro token from process arguments, allowing unauthorized access to Ubuntu Pro services.","url":"https://insights.sbomify.com/CVE-2026-102371/"}