CVE-2026-47256

opentelemetry-collector-contrib sentryexporter: Path traversal in Sentry exporter via attacker-controlled service.name reaches privileged Sentry API endpoints with operator bearer token

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-47256 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.154.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Apply the existing projectSlugRegexp to runtime-derived slugs, not only to operator config mappings:

import "regexp"                           

var runtimeSlugPattern = regexp.MustCompile(`^[a-zA-Z0-9_-]+$`)
                                        
func (s *endpointState) extractProjectSlug(attrs pcommon.Map) string {
    attrValue, exists := attrs.Get(s.attributeKey)                                                                                                          
    if !exists || attrValue.Type() != pcommon.ValueTypeStr {
        return ""                                                                                                                                           
    }                                     
    serviceName := attrValue.Str()                                                                                                                          
    if serviceName == "" {
        return ""                                                                                                                                           
    }                                     
    if s.projectMapping != nil {
        if mappedSlug, ok := s.projectMapping[serviceName]; ok {                                                                                            
            return mappedSlug
        }                                                                                                                                                   
    }                                     
    if !runtimeSlugPattern.MatchString(serviceName) {
        return "" // reject; drop the span or use a fallback default project
    }
    return serviceName                                                                                                                                      
}
                                                                                                                                                            
Alternatively, reject at URL construction:  
                                        
func (c *sentryClient) GetProjectKeys(ctx context.Context, orgSlug, projectSlug string) ([]projectKey, error) {
    if !runtimeSlugPattern.MatchString(projectSlug) {                                                                                                       
        return nil, fmt.Errorf("invalid project slug: %q", projectSlug)
    }                                                                                                                                                       
    baseURL := fmt.Sprintf("%s/api/0/projects/%s/%s/keys/", c.baseURL, orgSlug, projectSlug)
    // ...                                                                                                                                                  
}                                       

Apply the runtime regex to ALL slug-derived URL components (including orgSlug if it can ever be attacker-influenced), not just to config-time validation.

1. What is CVE-2026-47256? CVE-2026-47256 is a medium-severity path traversal vulnerability in github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (go), affecting versions < 0.154.0. It is fixed in 0.154.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-47256? CVE-2026-47256 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter are affected by CVE-2026-47256? github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (go) versions < 0.154.0 is affected.
4. Is there a fix for CVE-2026-47256? Yes. CVE-2026-47256 is fixed in 0.154.0. Upgrade to this version or later.
5. Is CVE-2026-47256 exploitable, and should I be worried? Whether CVE-2026-47256 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-47256 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-47256? Upgrade github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter to 0.154.0 or later.