Firebird Project is happy to announce general availability of Firebird 4.0.1 — the first point release in the Firebird 4.0 series.

This sub-release offers many bug fixes and also adds a few improvements, please refer to the Release Notes for the full list of changes.
Binary kits for Windows, Linux and Android platforms are immediately available for download.

Mark Rotteveel, the developer of Firebird JDBC driver Jaybird, has confirmed, that Jaybird does not depend on Log4j 2

Jaybird itself does not depend on Log4j 2.x, and as such is not directly affected by the recent Log4j 2 CVEs (but do check "Indirect risks" below). 

Jaybird 3 and higher by default use java.util.logging to log information. Jaybird 2.2 and earlier (all end-of-life) have an *optional* dependency on Log4j 1.x (which is not affected by the recent CVEs). This is only used when explicitly included on the classpath, and enabled using the system property FBLog4j or org.firebirdsql.jdbc.useLog4j[1]. This option was removed in Jaybird 3.

Indirect risks

If you're redirecting logging to Log4j 2 (e.g. from java.util.logging, or using a custom implementation of org.firebirdsql.logging.Logger), you may be vulnerable. If your applications are using Log4j 2, please make
sure to update to Log4j 2.17.0.  

The firebird-driver package provides official Python Database API 2.0-compliant driver. In addition to the minimal feature set of the standard Python DB API, this driver also exposes the new (interface-based) client API introduced in Firebird 3, and number of additional extensions and enhancements for convenient use of Firebird RDBMS. The driver is written as pure-Python package (requires Python 3.8+) on top of Firebird client library (fbclient.so/dll) using ctypes. Driver supports Firebird version 3.0 and higher.

You can download this driver from PyPI or install it using pip.

See the Changelog for full details.