{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-53582 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53582 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53582 is a high-severity vulnerability in opnsense core, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53582 and fix it if it is affected.\n\nWhat it is: CVE-2026-53582 is a high-severity vulnerability in opnsense core, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53582 in the wild and no public exploit code.\n\nAffected product: opnsense core. 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-53582/ (Markdown: https://insights.sbomify.com/CVE-2026-53582/index.md)","id":"CVE-2026-53582","markdown":"https://insights.sbomify.com/CVE-2026-53582/index.md","name":"CVE-2026-53582","record":{"aliases":["GHSA-xww7-76m6-mh2r"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"OPNsense firewall","requires_auth":"low_privilege","summary":"Privileged users can exploit XPath injection in the Trust module to extract sensitive secrets like keys and credentials from the configuration file.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-91","name":"XML Injection"},{"id":"CWE-643","name":"Improper Neutralization of Data within XPath Expressions"}],"description":"OPNsense is a FreeBSD based firewall and routing platform. Prior to version 26.1.10, the Trust module stores attacker-controlled certificate authority and certificate refid values and interpolates them into XPath expressions in src/opnsense/mvc/app/models/OPNsense/Trust/FieldTypes/CAsField.php and src/opnsense/mvc/app/models/OPNsense/Trust/FieldTypes/CertificatesField.php. A user with CA Manager or Certificate Manager privileges can submit a crafted refid and repeatedly retrieve the object to obtain a boolean refcount oracle, allowing values in config.xml to be recovered character by character. Exposed values can include password hashes, API credentials, certificate private keys, VPN key material, and high-availability credentials, enabling privilege escalation and compromise of other security domains. This issue is fixed in version 26.1.10.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-06-16","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-06-16T11:25:21Z","kind":"github_poc","ref":"https://github.com/eev4n/CVE-2026-53582","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":false,"headline":"OPNsense: XPATH Injection can disclose any secret in config.xml","id":"CVE-2026-53582","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":"libgit2: Inverted IP SubjectAltName Comparison in OpenSSL Backend","id":"CVE-2026-53583"},"packages":[],"prev":{"headline":"ntp: write path traversal","id":"CVE-2026-53581"},"products":["core"],"published":"2026-10-15","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["opnsense"]},"summary":"Privileged users can exploit XPath injection in the Trust module to extract sensitive secrets like keys and credentials from the configuration file.","url":"https://insights.sbomify.com/CVE-2026-53582/"}