BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-30472High confidence

Corosync — Stack-based Buffer Overflow

Corosync · Corosync

9.0CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.46% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Corosync Corosync and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcecorosyncVendor fix publishedDebian records a fixed source-package version for this release.3.1.9-2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcecorosyncVendor fix publishedDebian records a fixed source-package version for this release.3.1.7-1+deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcecorosyncVendor fix publishedDebian records a fixed source-package version for this release.3.1.9-2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcecorosyncVendor fix publishedDebian records a fixed source-package version for this release.3.1.9-2Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivecorosyncVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.3.1.7-1ubuntu3.1Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-7198

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.

Fix not verified
01

What, why and how

Corosync through 3.1.9, if encryption is disabled or the attacker knows the encryption key, has a stack-based buffer overflow in orf_token_endian_convert in exec/totemsrp.c via a large UDP packet.

What

Corosync through 3.1.9, if encryption is disabled or the attacker knows the encryption key, has a stack-based buffer overflow in orf_token_endian_convert in exec/totemsrp.c via a large UDP packet.

Why

A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Corosync through 3.1.9, if encryption is disabled or the attacker knows the encryption key, has a stack-based buffer overflow in orf_token_endian_convert in exec/totemsrp.c via a large UDP packet.

Why

A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Stack-based Buffer Overflow → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-121 ↗

CWE-121: Stack-based Buffer Overflow. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedCWE-121Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-1041Red Hat Enterprise Linux (corosync): Schwachstelle ermöglicht Codeausführung

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux in Corosync ausnutzen, um beliebigen Programmcode auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250326Security Bulletin 26 Mar 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 26 Mar 2025, published on 26 March 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0083Multiples vulnérabilités dans les produits IBM

rg/CVERecord?id=CVE-2025-0915 Référence CVE CVE-2025-1000 https://www.cve.org/CVERecord?id=CVE-2025-1000 Référence CVE CVE-2025-1493 https://www.cve.org/CVERecord?id=CVE-2025-1493 Référence CVE CVE-2025-1992 https://www.cve.org/CVERecord?id=CVE-2025-1992 Référence CVE CVE-2025-24970 https://www.cve.org/CVERecord?id=CVE-2025-24970 Référence CVE CVE-2025-2518 https://www.cve.org/CVERecord?id=CVE-2025-2518 Référence CVE CVE-2025-25193 https://www.cve.org/CVERecord?id=CVE-2025-25193 Référence CVE CVE-2025-2533 https://www.cve.org/CVERecord?id=CVE-2025-2533 Référence CVE CVE-2025-30065 https://www.cve.org/CVERecord?id=CVE-2025-30065 Référence CVE CVE-2025-30472 https://www.cve.org/CVERecord?id=CVE-2025-30472 Référence CVE CVE-2025-3050 https://www.cve.org/CVERecord?id=CVE-2025-3050 Référence CVE CVE-2025-33092 https://www.cve.org/CVERecord?id=CVE-2025-33092 Référence CVE CVE-2025-33114 https://www.cve.org/CVERecord?id=CVE-2025-33114 Référence CVE CVE-2025-33143 https://www.cve.org/CVERecord?id=CVE-2025-33143 Référence CVE CVE-2025-36010 https://www.cve.org/CVERecord?id=CVE-2025-36010 Référence CVE CVE-2025-36071 https://www.cve.org/CVERecord?id=CVE-2025-36071 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0760Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2025-24855 Référence CVE CVE-2025-24970 https://www.cve.org/CVERecord?id=CVE-2025-24970 Référence CVE CVE-2025-2533 https://www.cve.org/CVERecord?id=CVE-2025-2533 Référence CVE CVE-2025-25724 https://www.cve.org/CVERecord?id=CVE-2025-25724 Référence CVE CVE-2025-26791 https://www.cve.org/CVERecord?id=CVE-2025-26791 Référence CVE CVE-2025-27152 https://www.cve.org/CVERecord?id=CVE-2025-27152 Référence CVE CVE-2025-27516 https://www.cve.org/CVERecord?id=CVE-2025-27516 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-29927 https://www.cve.org/CVERecord?id=CVE-2025-29927 Référence CVE CVE-2025-30472 https://www.cve.org/CVERecord?id=CVE-2025-30472 Référence CVE CVE-2025-32386 https://www.cve.org/CVERecord?id=CVE-2025-32386 Référence CVE CVE-2025-32387 https://www.cve.org/CVERecord?id=CVE-2025-32387 Référence CVE CVE-2025-32421 https://www.cve.org/CVERecord?id=CVE-2025-32421 Référence CVE CVE-2025-32462 https://www.cve.org/CVERecord?id=CVE-2025-32462 Référence CVE CVE-2025-33092 https://www.cve.org/CVERecord?id=CVE-2025-33092 Référence CVE CVE-2025-33114 https://www.cve.org/CVERecord?id=CVE-2025-33114 Référence CVE CVE-2025-33143 https://www.cve.org/CVERecord?id=CVE-2025-33143 Référence CVE CVE-2025-3445 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0651Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2024-45491 Référence CVE CVE-2024-45492 https://www.cve.org/CVERecord?id=CVE-2024-45492 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-49342 https://www.cve.org/CVERecord?id=CVE-2024-49342 Référence CVE CVE-2024-49343 https://www.cve.org/CVERecord?id=CVE-2024-49343 Référence CVE CVE-2024-50602 https://www.cve.org/CVERecord?id=CVE-2024-50602 Référence CVE CVE-2025-0755 https://www.cve.org/CVERecord?id=CVE-2025-0755 Référence CVE CVE-2025-24970 https://www.cve.org/CVERecord?id=CVE-2025-24970 Référence CVE CVE-2025-27607 https://www.cve.org/CVERecord?id=CVE-2025-27607 Référence CVE CVE-2025-30472 https://www.cve.org/CVERecord?id=CVE-2025-30472 Référence CVE CVE-2025-33092 https://www.cve.org/CVERecord?id=CVE-2025-33092 Référence CVE CVE-2025-36097 https://www.cve.org/CVERecord?id=CVE-2025-36097 Référence CVE CVE-2025-47278 https://www.cve.org/CVERecord?id=CVE-2025-47278 Référence CVE CVE-2025-48387 https://www.cve.org/CVERecord?id=CVE-2025-48387 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-50182 https://www.cve.org/CVERecord?id=CVE-2025-50182 Référence CVE CVE-2025-5889 https://www.cve.org/CVERecord?id=CVE-2025-5889 Gestion détaillée du document le 01 août 2025 Version initiale A

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-003083Corosync における境界外書き込みに関する脆弱性

Corosync には、境界外書き込みに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
Corosync: ≤ 3.1.9
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 22 Mar 2025 · Last source change 3 Nov 2025, 18:09 UTC · CWE-121 · Stack-based Buffer Overflow

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-7198
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-30472 · cve.blacktree.nl