Skip to content
Fencer Intel
no cvss —

RUSTSEC-2025-0123 json

opentelemetry-jaeger crate is unmaintained

published 11mo ago modified 11mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

The `opentelemetry-jaeger` crate is deprecated and no longer actively maintained.

The Jaeger propagator implementation has been migrated to [opentelemetry-jaeger-propagator](https://crates.io/crates/opentelemetry-jaeger-propagator).

More information and examples of using OTLP with Jaeger can be found in [Introducing native support for OpenTelemetry in Jaeger](https://medium.com/jaegertracing/introducing-native-support-for-opentelemetry-in-jaeger-eb661be8183c) and [Exporting OTLP traces to Jaeger](https://github.com/open-telemetry/opentelemetry-rust/tree/main/examples/tracing-jaeger).

Is RUSTSEC-2025-0123 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io opentelemetry-jaeger
>=0.0.0-0
 no fix listed

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.