CVE-2026-34232
Firebirdsql Firebird 3.0.0 – 3.0.14
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2026-34232 is a high-severity Improper Handling of Syntactically Invalid Structure (CWE-228) vulnerability in Firebirdsql Firebird. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-34232 is a denial-of-service vulnerability in Firebird, an open-source relational database management system. The issue resides in the xdr_status_vector() function, which fails to properly handle the isc_arg_cstring type during decoding of an op_response packet. This mishandling triggers a server crash when such a type appears in the status vector. Affected versions include those prior to 5.0.4, 4.0.7, and 3.0.14. The vulnerability carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) and is associated with CWE-228 (Improper Handling of Syntactically Invalid Structure).
An unauthenticated remote attacker can exploit this vulnerability by sending a specially crafted op_response packet to the Firebird server, causing it to crash and resulting in a denial of service. No authentication, user interaction, or special privileges are required, making it accessible over the network with low complexity.
The Firebird project has addressed this issue in the following releases: 5.0.4, 4.0.7, and 3.0.14. Security practitioners should upgrade to one of these patched versions. Additional details are available in the project's security advisory at https://github.com/FirebirdSQL/firebird/security/advisories/GHSA-7jq3-6j3c-5cm2 and the corresponding release notes at https://github.com/FirebirdSQL/firebird/releases/tag/v3.0.14, https://github.com/FirebirdSQL/firebird/releases/tag/v4.0.7, and https://github.com/FirebirdSQL/firebird/releases/tag/v5.0.4.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23486
Vulnerability Data
Firebird is an open-source relational database management system. In versions prior to 5.0.4, 4.0.7 and 3.0.14, the xdr_status_vector() function does not handle the isc_arg_cstring type when decoding an op_response packet, causing a server crash when one is encountered in the…
more
status vector. An unauthenticated attacker can exploit this by sending a crafted op_response packet to the server. This issue has been fixed in versions 5.0.4, 4.0.7 and 3.0.14.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
SI-10 requires validity checks on information inputs, directly stopping syntactically malformed data from being processed without proper handling.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require robust input validation and syntax handling to prevent malformed-structure flaws.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect malformed-input issues but does not itself implement the handling logic.
Secure development life cycle mandates input validation and error handling that directly prevents improper handling of syntactically invalid structures.
Application security requirements include explicit rules for input validation and malformed-data handling.
Secure system architecture principles encourage robust input handling but do not prescribe the specific coding practice.
Secure coding explicitly requires validation of all input syntax and structure, directly eliminating CWE-228.