CVE-2026-0977
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 · uneditedIBM CICS Transaction Gateway for Multiplatforms 9.3 and 10.1 could allow a user to transfer or view files due to improper access controls.
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 · moderate confidenceIBM CICS Transaction Gateway for Multiplatforms versions 9.3 and 10.1 contains improper access control vulnerabilities that could allow authenticated or unauthorized users to transfer or view files on the system that should be restricted.
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= 9.3= 10.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
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.
-
Verify IBM CICS Transaction Gateway is installedLocate the CICS Transaction Gateway installation directory or check system inventory for product presence. Common locations include /opt/ibm/cics_tg or C:\Program Files\IBM\CICSTransactionGateway on Windows.Affected if IBM CICS Transaction Gateway for Multiplatforms is present on the system
-
Determine the installed versionRun theCTGVersion command or check the product version file in the installation directory. Compare the installed version against the affected versions 9.3 and 10.1.Affected if Installed version matches 9.3.x or 10.1.x
-
Confirm file transfer functionality is enabledInspect the CICS Transaction Gateway configuration files (typically ctg.ini or gateway.properties) for file transfer related settings or features. Check whether the DFHSCPL or file transfer channels are configured.Affected if File transfer or file viewing capabilities are enabled in the CICS TG configuration
-
Review access control configurationExamine the CICS TG security configuration files for file transfer authorization settings. Verify whether unrestricted file access paths or permissions are defined that could bypass intended restrictions.Affected if File transfer access controls are configured in a way that allows unrestricted or improperly restricted file access
A system is affected if IBM CICS Transaction Gateway versions 9.3 or 10.1 are installed with file transfer features enabled and the access control configuration permits unrestricted file transfers.
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.
From vendor dataApply IBM security patches for CVE-2026-0977 and review file transfer/access control configurations to ensure proper authorization enforcement per CICS security guidelines.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0977 — 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-2026-0977 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