How many CVEs have patched getKeyFile?

1 published CVEs changed getKeyFile in apache/camel, in 1 distinct patches totalling 12 changed lines, between 2026 and 2026.

What is the latest CVE that changed getKeyFile?

CVE-2026-40048 (Apache Camel PQC: Unsafe Deserialization from FileBasedKeyLifecycleManager), published 2026-04-27, changed lines 428 to 443 of components/camel-pqc/src/main/java/org/apache/camel/component/pqc/lifecycle/FileBasedKeyLifecycleManager.java.

How does getKeyFile compare to the rest of apache/camel?

apache/camel has 73 CVEs with a located fix in total; 1 of them changed getKeyFile.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

apache/camel

Function

getKeyFile

Name: getKeyFile in apache/camel: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

components/camel-pqc/src/main/java/org/apache/camel/component/pqc/lifecycle/FileBasedKeyLifecycleManager.java

Last patched April 27, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

12

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

getKeyFile in apache/camel was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 12 lines in total.

apache/camel has 73 CVEs with a located fix in total, so 1% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed getKeyFile, newest first, with the lines each fix touched.

Apache Camel PQC: Unsafe Deserialization from FileBasedKeyLifecycleManager
CVE-2026-40048 · lines 428–443 · +10 −2
Critical · CVSS 9.3
EPSS 0.5%2026-04-27

Get an alert when the next CVE fix lands in apache/camel, with the patched functions.

Monitor camel CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in apache/camel changed by the most CVE fixes.

getKeyMetadata3 CVEs · components/camel-pqc/src/main/java/org/apache/camel/component/pqc/lifecycle/FileBasedKeyLifecycleManager.java createExchange3 CVEs · components/camel-iggy/src/main/java/org/apache/camel/component/iggy/IggyFetchRecords.java initialize3 CVEs · components/camel-mail/src/main/java/org/apache/camel/component/mail/MailHeaderFilterStrategy.java getHeaderFilterStrategy3 CVEs · components/camel-coap/src/main/java/org/apache/camel/coap/CoAPEndpoint.java getHeaderFilterStrategy3 CVEs · components/camel-coap/src/main/java/org/apache/camel/coap/CoAPComponent.java sendEventNotification3 CVEs · components/camel-atmosphere-websocket/src/main/java/org/apache/camel/component/atmosphere/websocket/WebsocketConsumer.java

All patched functions in apache/camel

Frequently asked questions

Common questions about CVE fixes to getKeyFile.

How many CVEs have patched getKeyFile?: 1 published CVEs changed getKeyFile in apache/camel, in 1 distinct patches totalling 12 changed lines, between 2026 and 2026.
What is the latest CVE that changed getKeyFile?: CVE-2026-40048 (Apache Camel PQC: Unsafe Deserialization from FileBasedKeyLifecycleManager), published 2026-04-27, changed lines 428 to 443 of components/camel-pqc/src/main/java/org/apache/camel/component/pqc/lifecycle/FileBasedKeyLifecycleManager.java.
How does getKeyFile compare to the rest of apache/camel?: apache/camel has 73 CVEs with a located fix in total; 1 of them changed getKeyFile.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track apache/camel CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing