CVE-2025-14543
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Restriction of XML External Entity Reference vulnerability in RTI Connext Professional (Core Libraries) allows Serialized Data External Linking.This issue affects Connext Professional: from 7.4.0 before 7.7.0, from 7.0.0 before 7.3.1.1, from 6.1.0 before 6.1.*, from 6.0.0 before 6.0.*, from 5.3.0 before 5.3.*, from 4.3x before 5.2.*.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceXXE vulnerability in RTI Connext Professional Core Libraries allows attackers to inject malicious XML external entity references through serialized data, potentially enabling file disclosure, SSRF, or denial of service by exploiting improper restriction of XML external entity reference handling.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.3.0, <= 5.2.3>= 5.3.0, <= 5.3.1.45>= 6.0.0, <= 6.0.1.40>= 6.1.0, <= 6.1.2.27>= 7.0.0, < 7.3.1.1>= 7.4.0, < 7.7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify RTI Connext installation locationSearch for rti*.dll (Windows) or librti*.so (Linux) files in common installation directories such as /opt/rti, C:/Program Files/RTI, or check PATH environment variables for RTI binaries.Affected if RTI Connext libraries are present in the environment
-
Determine installed RTI Connext versionCheck the version of the installed RTI Connext libraries. On Windows, right-click the rti*.dll file and view Properties > Details for version info. On Linux, run 'ldd -v <library_path>' or check the librti*.so file version using 'file' or 'strings' commands. Alternatively, look for a VERSION.txt or release_notes.txt file in the installation directory.Affected if The installed version falls within any of these ranges: 4.3.0 to 5.2.3, 5.3.0 to 5.3.1.45, 6.0.0 to 6.0.1.40, 6.1.0 to 6.1.2.27, 7.0.0 to 7.3.1.0, or 7.4.0 to 7.6.x
-
Verify if XML serialization is in useSearch application logs, configuration files, or code for references to XML serialization, DataWriter serialization, or XML-based data exchange. RTI Connext uses XML for configuration and may serialize data in XML format. Look for .xml configuration files in the RTI directory or application data folders.Affected if XML-based serialization or XML configuration files are used with the affected RTI Connext installation
-
Inspect XML parser security configurationExamine RTI Connext configuration files (typically .xml or .xml.gz in the cfg or user_config directories) for parser settings. Check if there are any custom XML parser configurations that explicitly enable or disable external entity resolution. Look for elements related to XML parsing, DOCTYPE declarations, or entity processing.Affected if The XML parser is configured to allow external entity resolution (XXE) or no explicit disabling of external entities is found in parser configurations
The environment is affected if RTI Connext Professional is installed with a version in the affected ranges AND XML serialization/configuration is being used with external entity resolution enabled in the XML parser.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.3.1.17.7.0
Upgrade to patched versions (7.7.0+, 7.3.1.1+, or respective patched 6.1.x, 6.0.x, 5.3.x, 5.2.x releases). As interim measure, disable external entity resolution in XML parsers and implement strict XML input validation/sanitization.
Latest version in your major branch: 5.2.4+, 5.3.2+, 6.0.2+, 6.1.3+, or preferably 7.7.0+
- 1. Identify the currently installed RTI Connext Professional version by checking the installation directory or running the version command provided by RTI
- 2. Determine which major version branch your current installation belongs to (4.3.x-5.2.x, 5.3.x, 6.0.x, or 6.1.x)
- 3. For versions 4.3.0 to 5.2.3: upgrade to version 5.2.4 or later in the 5.2.x series
- 4. For versions 5.3.0 to 5.3.1.45: upgrade to version 5.3.2 or later in the 5.3.x series
- 5. For versions 6.0.0 to 6.0.1.40: upgrade to version 6.0.2 or later in the 6.0.x series
- 6. For versions 6.1.0 to 6.1.2.27: upgrade to version 6.1.3 or later in the 6.1.x series
- 7. Alternatively, consider upgrading to the latest 7.x release (7.7.0 or later) for the most recent security fixes
- 8. After upgrade, verify the XML parser configuration disables external entity processing as an additional defense-in-depth measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14543 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14543 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data