CVE-2026-40342: Firebird: Path Traversal + Arbitrary File Write Leads to Remote Code Execution

Published Apr 17, 2026
·
Updated

Firebird is an open-source relational database management system. In versions prior to 5.0.4, 4.0.7 and 3.0.14, the external engine plugin loader concatenates a user-supplied engine name into a filesystem path without filtering path separators or .. components. An authenticated user with CREATE FUNCTION privileges can use a crafted ENGINE name to load an arbitrary shared library from anywhere on the filesystem via path traversal. The library's initialization code executes immediately during loading, before Firebird validates the module, achieving code execution as the server's OS account. This issue has been fixed in versions 5.0.4, 4.0.7 and 3.0.14.

Affected Software

4 affected components
Firebird Firebird<5.0.4, <4.0.7, <3.0.14
firebirdsql Firebird<3.0.14
firebirdsql Firebird>=4.0.0<4.0.7
firebirdsql Firebird>=5.0.0<5.0.4

Event History

Apr 17, 2026
CVE Published
via MITRE·07:22 PM
Data Sourced
via MITRE·07:22 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-40342?

CVE-2026-40342 is classified as a critical vulnerability due to its potential to allow remote code execution.

2

How do I fix CVE-2026-40342?

To fix CVE-2026-40342, update Firebird to versions 5.0.4 or later, 4.0.7 or later, or 3.0.14 or later.

3

What are the risks associated with CVE-2026-40342?

The risks associated with CVE-2026-40342 include unauthorized access and control over the database system, leading to potential data breaches.

4

Which versions of Firebird are affected by CVE-2026-40342?

Versions of Firebird prior to 5.0.4, 4.0.7, and 3.0.14 are affected by CVE-2026-40342.

5

Is there a workaround for CVE-2026-40342?

There are no known workarounds for CVE-2026-40342; the only recommended action is to upgrade to a secure version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203