CVE-2026-46590

{
  "id": "CVE-2026-46590",
  "sourceIdentifier": "[email protected]",
  "published": "2026-07-06T09:16:37.147",
  "lastModified": "2026-10-25T15:10:00.147",
  "vulnStatus": "Analyzed",
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Deserialization of Untrusted Data vulnerability in Apache Camel PQC component.\n\nThe camel-pqc component persists post-quantum key metadata (KeyMetadata) through pluggable KeyLifecycleManager implementations. HashicorpVaultKeyLifecycleManager and AwsSecretsManagerKeyLifecycleManager read that metadata back from the configured secret backend by deserializing a Base64-wrapped value with a raw java.io.ObjectInputStream.readObject() and no ObjectInputFilter or class allow-list; the cast to KeyMetadata happens only after readObject() returns, so any readObject() side effects in a crafted object run before the type check. The same unfiltered legacy-migration read also remained in FileBasedKeyLifecycleManager (for the stored KeyPair and KeyMetadata). A principal who can write to the operator-controlled backend that holds these values - the HashiCorp Vault KV path, or the AWS Secrets Manager secret (requiring a Vault token or secretsmanager:PutSecretValue) - could store a crafted serialized object that is deserialized during normal key-lifecycle operations, potentially leading to code execution in the context of the application that manages the keys. This is an incomplete-remediation follow-on to CVE-2026-40048 (CAMEL-23200), which changed FileBasedKeyLifecycleManager to store metadata as JSON / PKCS#8 / X.509 but did not add an ObjectInputFilter, did not cover the Vault and AWS sibling managers, and left FileBasedKeyLifecycleManager's own legacy-migration deserialization unfiltered.\nThis issue affects Apache Camel: from 4.18.0 before 4.18.3, from 4.19.0 before 4.21.0.\n\nUsers are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.3. For deployments that cannot upgrade immediately, restrict write access to the key backend so that only the application's own identity can write the camel-pqc secrets (least-privilege HashiCorp Vault policies and secretsmanager:PutSecretValue IAM), and keep the PQC key material in a backend separate from any data that less-trusted principals can write."
    },
    {
      "lang": "es",
      "value": "Vulnerabilidad de deserialización de datos no confiables en el componente Apache Camel PQC.\n\nEl componente camel-pqc persiste metadatos de clave post-cuántica (KeyMetadata) a través de implementaciones conectables de KeyLifecycleManager. HashicorpVaultKeyLifecycleManager y AwsSecretsManagerKeyLifecycleManager leen esos metadatos del backend de secretos configurado al deserializar un valor envuelto en Base64 con un java.io.ObjectInputStream.readObject() en bruto y sin ObjectInputFilter o lista de permitidos de clases; la conversión a KeyMetadata ocurre solo después de que readObject() retorna, por lo que cualquier efecto secundario de readObject() en un objeto manipulado se ejecuta antes de la verificación de tipo. La misma lectura de migración heredada sin filtrar también permaneció en FileBasedKeyLifecycleManager (para el KeyPair y KeyMetadata almacenados). Un principal que puede escribir en el backend controlado por el operador que contiene estos valores - la ruta KV de HashiCorp Vault, o el secreto de AWS Secrets Manager (que requiere un token de Vault o secretsmanager:PutSecretValue) - podría almacenar un objeto serializado manipulado que se deserializa durante las operaciones normales del ciclo de vida de la clave, lo que podría llevar a la ejecución de código en el contexto de la aplicación que gestiona las claves. Esto es una continuación de remediación incompleta de CVE-2026-40048 (CAMEL-23200), que cambió FileBasedKeyLifecycleManager para almacenar metadatos como JSON / PKCS#8 / X.509 pero no añadió un ObjectInputFilter, no cubrió los gestores hermanos de Vault y AWS, y dejó la propia deserialización de migración heredada de FileBasedKeyLifecycleManager sin filtrar.\nEste problema afecta a Apache Camel: desde 4.18.0 antes de 4.18.3, desde 4.19.0 antes de 4.21.0.\n\nSe recomienda a los usuarios actualizar a la versión 4.21.0, que corrige el problema. Si los usuarios están en la rama de versiones LTS 4.18.x, entonces se sugiere que actualicen a 4.18.3. Para implementaciones que no pueden actualizarse inmediatamente, restrinja el acceso de escritura al backend de claves de modo que solo la propia identidad de la aplicación pueda escribir los secretos de camel-pqc (políticas de menor privilegio de HashiCorp Vault y secretsmanager:PutSecretValue IAM), y mantenga el material de clave PQC en un backend separado de cualquier dato que los principales menos confiables puedan escribir."
    }
  ],
  "affected": [
    {
      "source": "[email protected]",
      "affectedData": [
        {
          "vendor": "Apache Software Foundation",
          "product": "Apache Camel",
          "defaultStatus": "unaffected",
          "collectionURL": "https://repo.maven.apache.org/maven2",
          "packageName": "org.apache.camel:camel-pqc",
          "versions": [
            {
              "version": "4.18.0",
              "lessThan": "4.18.3",
              "versionType": "semver",
              "status": "affected"
            },
            {
              "version": "4.19.0",
              "lessThan": "4.21.0",
              "versionType": "semver",
              "status": "affected"
            }
          ]
        }
      ]
    }
  ],
  "metrics": {
    "cvssMetricV31": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary",
        "cvssData": {
          "version": "3.1",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
          "baseScore": 8.8,
          "baseSeverity": "HIGH",
          "attackVector": "NETWORK",
          "attackComplexity": "LOW",
          "privilegesRequired": "LOW",
          "userInteraction": "NONE",
          "scope": "UNCHANGED",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "availabilityImpact": "HIGH"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 5.9
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "timestamp": "2026-07-06T19:15:54.431681Z",
          "id": "CVE-2026-46590",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "role": "CISA Coordinator",
          "version": "2.0.3"
        }
      }
    ]
  },
  "weaknesses": [
    {
      "source": "[email protected]",
      "type": "Secondary",
      "description": [
        {
          "lang": "en",
          "value": "CWE-502"
        }
      ]
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "operator": "OR",
          "negate": false,
          "cpeMatch": [
            {
              "vulnerable": true,
              "criteria": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
              "versionStartIncluding": "4.18.0",
              "versionEndExcluding": "4.18.3",
              "matchCriteriaId": "3F672322-AA52-4621-B687-76B5AC9D619F"
            },
            {
              "vulnerable": true,
              "criteria": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
              "versionStartIncluding": "4.19.0",
              "versionEndExcluding": "4.21.0",
              "matchCriteriaId": "1C2A1A7A-FADC-470F-8265-FA126AFD94ED"
            }
          ]
        }
      ]
    }
  ],
  "references": [
    {
      "url": "https://camel.apache.org/security/CVE-2026-46590.html",
      "source": "[email protected]",
      "tags": [
        "Vendor Advisory"
      ]
    }
  ]
}