CVE-2026-45404

OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 0.11.0 through 1.44.0, the OpenTracing bridge's bridgeSpan contains an unsynchronized extraBaggageItems map which can cause a panic. Because Go maps are not safe for concurrent read/write access, concurrent SetBaggageItem and correlation.MapFromContext calls on the same hooked bridgeSpan can trigger a fatal runtime error—such as concurrent map read and map write or concurrent map iteration and map write—terminating the process and causing denial of service. This issue is fixed in version 1.45.0.

CVSS

No CVSS.

References

Link	Resource
https://github.com/open-telemetry/opentelemetry-go/commit/93a693edeed0e07ce5ebd1dfe67af42d1e2055d8
https://github.com/open-telemetry/opentelemetry-go/pull/8693
https://github.com/open-telemetry/opentelemetry-go/releases/tag/v1.45.0
https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-42cj-99w8-cp2p
https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-42cj-99w8-cp2p

Configurations

No configuration.

History

12 Oct 2026, 15:10

Type	Values Removed	Values Added
Summary		(es) OpenTelemetry-Go es la implementación de Go de OpenTelemetry. Desde la versión 0.11.0 hasta la 1.44.0, el bridgeSpan del bridge de OpenTracing contiene un mapa extraBaggageItems sin sincronizar que puede causar un panic. Debido a que los mapas de Go no son seguros para el acceso concurrente de lectura y escritura, las llamadas concurrentes a SetBaggageItem y correlation.MapFromContext en el mismo bridgeSpan enganchado pueden desencadenar un error de tiempo de ejecución fatal -como lectura y escritura concurrente de mapas o iteración y escritura concurrente de mapas-, terminando el proceso y causando denegación de servicio. Este problema está solucionado en la versión 1.45.0.

Information

Published : 2026-08-24 22:16

Updated : 2026-10-12 15:10

NVD link : CVE-2026-45404

Mitre link : CVE-2026-45404

CVE.ORG link : CVE-2026-45404

JSON object : View

Products Affected

No product.

CWE

CWE-362

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CWE-667

Improper Locking

{"id": "CVE-2026-45404", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-45404", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-27T14:18:31.891717Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 5.9, "Automatable": "NOT_DEFINED", "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "open-telemetry", "product": "opentelemetry-go", "versions": [{"status": "affected", "version": ">= 0.11.0, < 1.45.0"}]}]}], "published": "2026-08-24T22:16:53.020", "references": [{"url": "https://github.com/open-telemetry/opentelemetry-go/commit/93a693edeed0e07ce5ebd1dfe67af42d1e2055d8", "source": "security-advisories@github.com"}, {"url": "https://github.com/open-telemetry/opentelemetry-go/pull/8693", "source": "security-advisories@github.com"}, {"url": "https://github.com/open-telemetry/opentelemetry-go/releases/tag/v1.45.0", "source": "security-advisories@github.com"}, {"url": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-42cj-99w8-cp2p", "source": "security-advisories@github.com"}, {"url": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-42cj-99w8-cp2p", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-362"}, {"lang": "en", "value": "CWE-667"}]}], "descriptions": [{"lang": "en", "value": "OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 0.11.0 through 1.44.0, the OpenTracing bridge's bridgeSpan contains an unsynchronized extraBaggageItems map which can cause a panic. Because Go maps are not safe for concurrent read/write access, concurrent SetBaggageItem and correlation.MapFromContext calls on the same hooked bridgeSpan can trigger a fatal runtime error\u2014such as concurrent map read and map write or concurrent map iteration and map write\u2014terminating the process and causing denial of service. This issue is fixed in version 1.45.0."}, {"lang": "es", "value": "OpenTelemetry-Go es la implementaci\u00f3n de Go de OpenTelemetry. Desde la versi\u00f3n 0.11.0 hasta la 1.44.0, el bridgeSpan del bridge de OpenTracing contiene un mapa extraBaggageItems sin sincronizar que puede causar un panic. Debido a que los mapas de Go no son seguros para el acceso concurrente de lectura y escritura, las llamadas concurrentes a SetBaggageItem y correlation.MapFromContext en el mismo bridgeSpan enganchado pueden desencadenar un error de tiempo de ejecuci\u00f3n fatal -como lectura y escritura concurrente de mapas o iteraci\u00f3n y escritura concurrente de mapas-, terminando el proceso y causando denegaci\u00f3n de servicio. Este problema est\u00e1 solucionado en la versi\u00f3n 1.45.0."}], "lastModified": "2026-10-12T15:10:00.207", "sourceIdentifier": "security-advisories@github.com"}