# Apache Camel-PQC: The HashiCorp Vault and AWS Secrets Manager key-lifecycle managers deserialize persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter (incomplete remediation of CVE-2026-40048) Advisory record · `GHSA-857v-xvh8-7hjc` - **Identifiers:** `GHSA-857v-xvh8-7hjc` · `CVE-2026-46590` - **State:** Confirmed - **Severity:** CVSS 8.8 High - **Critical:** No - **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html) - **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md) - **Published:** 6 Jul 2026 - **Updated:** 28 Aug 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 6 Jul 2026, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.apache.camel:camel-pqc` (Maven): affected `>=4.18.0, <4.18.3 || >=4.19.0, <4.21.0`; fixed in `4.18.3`, `4.21.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache Camel camel-pqc versions 4.18.0 to before 4.18.3 and 4.19.0 to before 4.21.0 are vulnerable to unsafe deserialization in the HashiCorp Vault and AWS Secrets Manager key-lifecycle managers. An attacker who can write to the configured Vault path or AWS secret could store a crafted serialized object that may lead to code execution in the application. Upgrade to camel-pqc 4.21.0, or 4.18.3 on the 4.18.x LTS stream; until then, restrict write access to the key backend to the application's own identity. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.0084, the 58th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:19 UTC: First seen by agentprime - 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-857v-xvh8-7hjc) ## Sources - [GitHub Advisory Database: GHSA-857v-xvh8-7hjc](https://github.com/advisories/GHSA-857v-xvh8-7hjc) - [OSV: GHSA-857v-xvh8-7hjc](https://osv.dev/vulnerability/GHSA-857v-xvh8-7hjc) - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .