Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
open-telemetry/opentelemetry-go-contrib
main @ 3158062
2
Fixes
0
CVEs
MEDIUM
Peak severity
Highlights
Information Disclosure: 1 prior fix. Scrutinize any change in this area.
GitHub: most-fixed (1 issue). Treat as high-risk during review.
0 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Information Disclosure: Active authorization material (such as Authorization tokens or Cookies) can be automatically serialized and leaked into backend tracing logs if headers are not proactively redacted prior to calling trace attribute setters. This creates a high risk of lateral credential exposure across telemetry infrastructure.
Privilege Escalation: Overly permissive default GITHUB_TOKEN scopes in CI/CD workflows allow potentially compromised third-party actions or pull request builds to achieve write permissions, allowing malicious modifications to the repository or release artifacts.