{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-101322 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-101322 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-101322 is a high-severity vulnerability in Eclipse BaSyx AAS Web UI, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-101322 and fix it if it is affected.\n\nWhat it is: CVE-2026-101322 is a high-severity vulnerability in Eclipse BaSyx AAS Web UI, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-101322 in the wild and no public exploit code.\n\nAffected product: Eclipse BaSyx AAS Web UI. 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-101322/ (Markdown: https://insights.sbomify.com/CVE-2026-101322/index.md)","id":"CVE-2026-101322","markdown":"https://insights.sbomify.com/CVE-2026-101322/index.md","name":"CVE-2026-101322","record":{"aliases":["GHSA-g9cm-gpjq-m9vq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Eclipse BaSyx Web UI","requires_auth":"none","summary":"Attackers can steal authentication tokens by tricking users into visiting crafted links, allowing unauthorized access to protected services.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"description":"In Eclipse BaSyx AAS Web UI versions v2-241220 through releases before v2-260924, the shared request handler attached the selected infrastructure's `Authorization` header to outgoing requests without checking the destination origin. In deployments using authentication, an attacker could induce a user to open a crafted Web UI link whose `aas` or `path` query parameter points to an attacker-controlled endpoint. The user's browser would then send the configured Basic Authentication credentials, Bearer token, or an available OAuth2 access token to that endpoint. The attacker could reuse the disclosed credential to access protected AAS services with the victim's privileges. The issue is fixed in v2-260924.","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":"Information disclosure in Eclipse BaSyx AAS Web UI","id":"CVE-2026-101322","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":"Fluent Forms \u003c= 6.2.14 - Reflected Cross-Site Scripting via '{get.*}' Editor SmartCode Parameter","id":"CVE-2026-101324"},"packages":[],"prev":{"headline":"Multiple vulnerabilities in bhyve device models","id":"CVE-2026-101311"},"products":["Eclipse BaSyx AAS Web UI"],"published":"2026-10-01","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-10-01","vendors":["Eclipse Foundation"]},"summary":"Attackers can steal authentication tokens by tricking users into visiting crafted links, allowing unauthorized access to protected services.","url":"https://insights.sbomify.com/CVE-2026-101322/"}