{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-81821 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81821 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81821 is a high-severity vulnerability in AVEVA Pipeline Integrity Monitor, published on 8 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-81821 and fix it if it is affected.\n\nWhat it is: CVE-2026-81821 is a high-severity vulnerability in AVEVA Pipeline Integrity Monitor, published on 8 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-81821 in the wild and no public exploit code.\n\nAffected product: AVEVA Pipeline Integrity Monitor. 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-81821/ (Markdown: https://insights.sbomify.com/CVE-2026-81821/index.md)","id":"CVE-2026-81821","markdown":"https://insights.sbomify.com/CVE-2026-81821/index.md","name":"CVE-2026-81821","record":{"aliases":["GHSA-xgr2-pj73-vrpj"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Pipeline Integrity Monitor","requires_auth":"low_privilege","summary":"An attacker with file access can decrypt sensitive data in AVEVA Pipeline Integrity Monitor projects due to a hard-coded cryptographic key.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"The vulnerability, if exploited, could allow a miscreant with read access to PIMBoards project files to decrypt and view sensitive information.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"AVEVA Pipeline Integrity Monitor Use of hard-coded cryptographic key","id":"CVE-2026-81821","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"AVEVA Pipeline Integrity Monitor Use of a Broken or Risky Cryptographic Algorithm","id":"CVE-2026-81822"},"packages":[],"prev":{"headline":"Flowintel HTML Injection in MISP Case History Timeline via Crafted Object Attributes","id":"CVE-2026-81820"},"products":["Pipeline Integrity Monitor"],"published":"2026-09-08","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":"total"},"state":"PUBLISHED","updated":"2026-09-11","vendors":["AVEVA"]},"summary":"An attacker with file access can decrypt sensitive data in AVEVA Pipeline Integrity Monitor projects due to a hard-coded cryptographic key.","url":"https://insights.sbomify.com/CVE-2026-81821/"}