CVE-2025-36018

MEDIUMNVD 6.56.5—Trending — 3 sources updated this week

6.5

IBM Concert 1.0.0 through 2.1.0 for Z hub component is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts.

CVSS v3: 6.5
EG Score: 6.5(medium)
EPSS: 5.4%
KEV: Not listed

Published

February 17, 2026

Last Modified

February 18, 2026

References (1)

psirt@ushttps://www.ibm.com/support/pages/node/7260162

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-352Cross-Site Request Forgery (CSRF)

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 13:47 UTCEG score recompute
2026-05-29 13:47 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2025-36018?

CVE-2025-36018 is a medium vulnerability published on February 17, 2026. IBM Concert 1.0.0 through 2.1.0 for Z hub component is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts.

When was CVE-2025-36018 disclosed?

CVE-2025-36018 was first published in the National Vulnerability Database on February 17, 2026, with the most recent update on February 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2025-36018 actively exploited?

CVE-2025-36018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2025-36018?

CVE-2025-36018 has a CVSS v3 base score of 6.5 (NVD).

How do I remediate CVE-2025-36018?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-36018, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-36018

Explore →

Is Your Infrastructure Affected by CVE-2025-36018?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2025-36018

📅 Published

🔄 Last Modified

🔗 References (1)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2025-36018?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (1)

Frequently asked(5)

Related CVEs(same CWE)