Skip to content

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

Moderate severity GitHub Reviewed Published Jun 17, 2026 in open-telemetry/opentelemetry-collector-contrib • Updated Jun 18, 2026

Package

gomod github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter (Go)

Affected versions

< 0.154.0

Patched versions

0.154.0

Description

Summary

The Sentry exporter constructs Sentry API URLs by interpolating the span's service.name resource attribute into the URL path without validation. Because
service.name is controlled by remote OTLP senders and the operator-configured bearer token is attached to every request, a crafted service name can reach
arbitrary Sentry API endpoints reachable by that token — including privileged admin, organization, and member endpoints within the configured Sentry
organization.

Affected

  • exporter/sentryexporter/sentry_exporter.go (lines 715–737) — extractProjectSlug returns the attacker-controlled service.name directly as the slug.
  • exporter/sentryexporter/sentry_exporter.go (lines 745–809) — getOrCreateProjectEndpoint passes the raw slug to GetOTLPEndpoints at line 761.
  • exporter/sentryexporter/sentry_client.go (lines 190–244) — GetProjectKeys interpolates the slug into fmt.Sprintf URL path and attaches the operator bearer
    token on line 207.
  • exporter/sentryexporter/sentry_client.go (lines 327–363) — GetOTLPEndpoints calls GetProjectKeys on line 329 with the raw slug.
  • exporter/sentryexporter/config.go (lines 55–108) — projectSlugRegexp is applied only to operator config mappings inside validateRoutingConfig, never to
    runtime-derived slugs.

Root cause

  1. extractProjectSlug (sentry_exporter.go:715–737) reads service.name from pcommon.Resource.Attributes() without schema validation and returns the raw
    string on line 736.
  2. GetProjectKeys (sentry_client.go:192) calls fmt.Sprintf("%s/api/0/projects/%s/%s/keys/", c.baseURL, orgSlug, projectSlug). The slug is treated as a
    single path segment but no validation is performed.
  3. projectSlugRegexp (config.go:58) — defined as ^[a-z0-9_-]{1,50}$ — is referenced only inside validateRoutingConfig on line 98 (config-time only). No
    runtime callsite exists.
  4. Go net/http preserves literal .. and / characters in URL paths when constructed via fmt.Sprintf.
  5. The operator-configured DSN / bearer token is attached unconditionally to every outbound request (sentry_client.go:207): req.Header.Set("Authorization",
    fmt.Sprintf("Bearer %s", c.authToken)).

Exploitation

Primary: query-string injection (reliable across all deployments)

Attacker emits service.name = "foo?injected_query=".

URL becomes https://sentry.io/api/0/projects/ORG-SLUG/foo?injected_query=/keys/.

The trailing /keys/ is consumed as part of the query string. The resource endpoint is /api/0/projects/ORG-SLUG/foo. The attacker can reach any GET-based
Sentry API endpoint reachable by the bearer token. This vector is not dependent on server-side path normalization and works in all deployment
configurations.

Secondary: path traversal (nginx-dependent)

Attacker emits a span with service.name = "foo/../../members".

Resulting URL: https://sentry.io/api/0/projects/ORG-SLUG/foo/../../members/keys/

After server-side normalization (nginx resolves .. segments): https://sentry.io/api/0/projects/ORG-SLUG/members/keys/

The operator bearer token authenticates the request. Effectiveness depends on whether the Sentry deployment normalizes .. segments before routing (standard
nginx behaviour).

Amplified: telemetry redirect for data exfiltration

Attacker-owned Sentry project slug → span data for other applications is exported to an attacker-controlled Sentry project, leaking operational telemetry.
The collector fetches the DSN/keys for the attacker's slug and subsequently forwards legitimate traces/logs to the attacker-controlled destination.

Threat model

  • Attacker capabilities: remote OTLP trace sender (application-level span emission).
  • Operator capabilities: configures Sentry DSN, bearer token, base URL; sets up receiver pipeline.
  • The attacker does NOT control operator YAML. The attacker DOES control resource attribute values on spans they emit.

Realistic deployment

  • Kubernetes cluster with OpenTelemetry Collector forwarding traces from multiple applications to Sentry SaaS or self-hosted Sentry.
  • One compromised or malicious application reaches the collector via OTLP.
  • The collector is configured with a valid Sentry bearer token for the organization.

Remediation

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.

Credit

Reported by independent security research by Martin Brodeur.

References

Published to the GitHub Advisory Database Jun 18, 2026
Reviewed Jun 18, 2026
Last updated Jun 18, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

Weaknesses

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Learn more on MITRE.

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Learn more on MITRE.

CVE ID

CVE-2026-47256

GHSA ID

GHSA-4jvg-4jfx-fmhc

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.