# Apache Camel-PQC: The AWS Secrets Manager key-lifecycle manager deserializes persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter Advisory record · `GHSA-7cmx-qjh8-7v3v` - **Identifiers:** `GHSA-7cmx-qjh8-7v3v` · `CVE-2026-43867` - **State:** Confirmed - **Severity:** CVSS 9.8 Critical - **Critical:** Yes: CVSS 9+ - **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:** 26 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. ## Critical Critical, because: - CVSS score 9.8: 9.0 or more. How we decide what’s critical: ## 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 from 4.18.0 before 4.18.3 and from 4.19.0 before 4.21.0 are affected. The AWS Secrets Manager key-lifecycle manager deserializes stored key metadata with Java serialization and no class filter, so a principal with permission to write the secret (secretsmanager:PutSecretValue) could store a crafted object that may lead to code execution in the application managing the keys. Upgrade to camel-pqc 4.21.0, or 4.18.3 on the 4.18.x LTS stream. Until then, limit PutSecretValue on the key metadata secret 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 - 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.0093, the 60th percentile, on 9 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-7cmx-qjh8-7v3v) ## Sources - [GitHub Advisory Database: GHSA-7cmx-qjh8-7v3v](https://github.com/advisories/GHSA-7cmx-qjh8-7v3v) - [OSV: GHSA-7cmx-qjh8-7v3v](https://osv.dev/vulnerability/GHSA-7cmx-qjh8-7v3v) - - - - - - - - - - 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: .