Safeguard
Vulnerability Analysis•

CVE-2022-34309: Medium Weak Cryptography in IBM CICS TX 11.1

CVE-2022-34309 is weak cryptography in IBM CICS TX Standard and Advanced 11.1, scored 5.9. Apply IBM's interim fix for defect 127917 on each edition.

Safeguard Security Team
3 min read

CVE-2022-34309 is a medium severity flaw in IBM CICS TX Standard and Advanced 11.1, scored 5.9. It uses weaker than expected cryptographic algorithms that could let an attacker decrypt highly sensitive information. IBM provides an interim fix for defect 127917 for each edition.

What's affected

IBM's two bulletins, one for CICS TX Standard and one for CICS TX Advanced, list version 11.1 as affected. IBM recommends applying the interim fix for defect 127917. It lists no workarounds or mitigations. Both were first published on 28 October 2022, and the X-Force ID is 229440.

IBM scores the flaw 5.9 using CVSS 3.0, with network vector, high attack complexity, no privileges, no user interaction and a high confidentiality impact. NVD matches at 5.9 Medium.

The sibling CVE-2022-34310 has the same text and score but a different defect, 127918. Two different weak algorithm issues exist, so apply both fixes. The record's kev flag is false.

The bulletins do not name the algorithms, so I will not guess.

Weakness class per the record: CWE-327.

How to check if you're exposed

Check the CICS TX version and the interim fixes installed through your IBM installation records. The affected release is 11.1 in both editions.

Open the IBM bulletin for your edition, download the interim fix for defect 127917, and compare it with the fixes recorded on your system.

If you manage many CICS TX regions, collect their versions and fix levels from your deployment tooling in one pass.

What to do now

  1. Identify CICS TX Standard and Advanced 11.1 installations.
  2. Apply the interim fix for defect 127917 from the IBM bulletin for your edition.
  3. Also apply the fix for defect 127918, which covers the sibling CVE-2022-34310.
  4. Review which traffic relies on the affected cryptography and plan key rotation if IBM's guidance calls for it.

Why it matters

Weak cryptographic algorithms (CWE-327) give less protection than the key sizes or protocol names suggest. An attacker who can capture traffic or data may be able to decrypt it with feasible effort.

The high attack complexity in the score reflects that exploitation needs a good position and effort. The impact is high confidentiality because the target is sensitive data.

For mainframe style transaction systems the data is often financial or personal, so the fix deserves attention despite the medium rating.

Quick check

Is there a workaround?

IBM lists none. Apply the interim fix for the defect that matches your edition.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.