Vulnerability Database · Go · Package report

github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor: vulnerability history, versions and safety

github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor v0.163.0 i

Updated on 23 Oct 2026

Good news: v0.163.0, the version you would install today, has no known vulnerabilities.

Package health score 91/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on v0.163.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.163.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.163.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 5,011 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.163.1-0.20261020224815-cf360012835b 20 Oct 2026 none Apache-2.0 — Details →
v0.163.1-0.20261020112510-9c8f253c6a6c 20 Oct 2026 none Apache-2.0 — Details →
v0.163.1-0.20261020055728-0fd3033f53bd 20 Oct 2026 none Apache-2.0 — Details →
v0.163.1-0.20261019205253-229c99f494a8 19 Oct 2026 none Apache-2.0 — Details →
v0.163.1-0.20261019112045-9d3efa7f87be 19 Oct 2026 none Apache-2.0 — Details →
v0.163.1-0.20261019072919-0f1a5d7434d1 19 Oct 2026 none Apache-2.0 — Details →
v0.163.1-0.20261015210534-701867a218d0 15 Oct 2026 none Apache-2.0 — Details →
v0.163.1-0.20261015192808-cd37ea915187 15 Oct 2026 none Apache-2.0 — Details →
v0.163.1-0.20261015174624-dcdc857dfc2e 15 Oct 2026 none Apache-2.0 — Details →
v0.163.1-0.20261015162134-c4f723c3ea8d 15 Oct 2026 none Apache-2.0 — Details →
v0.163.1-0.20261015065750-d810415b1216 15 Oct 2026 none Apache-2.0 — Details →
v0.163.1-0.20261014210708-ac07dedd1754 14 Oct 2026 none Apache-2.0 — Details →
v0.163.1-0.20261014062238-c9225787610f 14 Oct 2026 none Apache-2.0 — Details →
v0.163.0 14 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261013144830-a7d1efbf1c46 13 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261012235616-be4fde21112d 12 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261012203520-d4b055b56f2e 12 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261010131741-5ca2c088522a 10 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261009213710-c766745fdaed 09 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261009174001-7e40912bfdab 09 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261009171739-68be81816b0b 09 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261009064638-a42af6edafc0 09 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261008064532-104b0be085a1 08 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261007074611-d1626f4c7518 07 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261006085625-e88ddd5d027b 06 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261006022125-a581d94ee4d0 06 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261005205258-3d5342b8bb73 05 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261005193909-0a54d2beec44 05 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261002194846-787258321e67 02 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261002073719-732a8c02cd0c 02 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20261001051435-9ad9070c1fbb 01 Oct 2026 none Apache-2.0 — Details →
v0.162.1-0.20260930075749-fb5604fd71eb 30 Sep 2026 none Apache-2.0 — Details →
v0.162.0 29 Sep 2026 none Apache-2.0 — Details →
v0.161.1-0.20260915112948-d6d43a6748bc 15 Sep 2026 none Apache-2.0 — Details →
v0.161.0 15 Sep 2026 none Apache-2.0 — Details →
v0.160.1-0.20260915070237-0333e0585cb4 15 Sep 2026 none Apache-2.0 — Details →
v0.160.1-0.20260913143606-9861a82ba110 13 Sep 2026 none Apache-2.0 — Details →
v0.160.1-0.20260911234939-933f7c7ff041 11 Sep 2026 none Apache-2.0 — Details →
v0.160.1-0.20260905005929-a67d7654db61 05 Sep 2026 none Apache-2.0 — Details →
v0.160.0 02 Sep 2026 none Apache-2.0 — Details →
v0.159.0 17 Aug 2026 none Apache-2.0 — Details →
v0.158.0 04 Aug 2026 none Apache-2.0 — Details →
v0.157.1-0.20260721145201-bea801816246 21 Jul 2026 none Apache-2.0 — Details →
v0.157.0 21 Jul 2026 none Apache-2.0 — Details →
v0.156.0 07 Jul 2026 none Apache-2.0 — Details →
v0.155.1-0.20260624170339-c0368699cbc3 24 Jun 2026 none Apache-2.0 — Details →
v0.155.0 23 Jun 2026 none Apache-2.0 — Details →
v0.154.1-0.20260616190457-a0e863162ff2 16 Jun 2026 none Apache-2.0 — Details →
v0.154.1-0.20260616145356-ba8d823d2e72 16 Jun 2026 none Apache-2.0 — Details →
v0.154.1-0.20260612030934-699a7669a8fe 12 Jun 2026 none Apache-2.0 — Details →
v0.154.1-0.20260610215448-0abbb14a405b 10 Jun 2026 none Apache-2.0 — Details →
v0.154.1-0.20260609230519-defe51cd207d 09 Jun 2026 none Apache-2.0 — Details →
v0.154.1-0.20260609161553-933b942262b1 09 Jun 2026 none Apache-2.0 — Details →
v0.154.0 09 Jun 2026 none Apache-2.0 — Details →
v0.153.1-0.20260608050257-98f1873417a2 08 Jun 2026 none Apache-2.0 — Details →
v0.153.1-0.20260605062325-01d379908656 05 Jun 2026 none Apache-2.0 — Details →
v0.153.1-0.20260604065726-703876e8cb98 04 Jun 2026 none Apache-2.0 — Details →
v0.153.1-0.20260603063242-ec03770fdfe0 03 Jun 2026 none Apache-2.0 — Details →
v0.153.1-0.20260602065253-b75cc883ea08 02 Jun 2026 none Apache-2.0 — Details →
v0.153.1-0.20260531063951-6698bc24dc8e 31 May 2026 none Apache-2.0 — Details →
v0.153.1-0.20260529080419-390867eec19e 29 May 2026 none Apache-2.0 — Details →
v0.153.1-0.20260528075435-5837a8a663e8 28 May 2026 none Apache-2.0 — Details →
v0.153.1-0.20260527073217-9f7debae0338 27 May 2026 none Apache-2.0 — Details →
v0.153.1-0.20260526162243-ed53d7c6d108 26 May 2026 none Apache-2.0 — Details →
v0.153.1-0.20260526153022-6288f5cf9e32 26 May 2026 none Apache-2.0 — Details →
v0.153.1-0.20260526070041-c81e44199338 26 May 2026 none Apache-2.0 — Details →
v0.153.0 26 May 2026 none Apache-2.0 — Details →
v0.152.1-0.20260518070759-91238030c5ab 18 May 2026 none Apache-2.0 — Details →
v0.152.1-0.20260515070804-a4172e65b048 15 May 2026 none Apache-2.0 — Details →
v0.152.1-0.20260514005723-8b64c738aa54 14 May 2026 none Apache-2.0 — Details →
v0.152.1-0.20260513071206-1ff7ddbf5695 13 May 2026 none Apache-2.0 — Details →
v0.152.1-0.20260512063106-b35feafebc4f 12 May 2026 none Apache-2.0 — Details →
v0.152.0 11 May 2026 none Apache-2.0 — Details →
v0.151.1-0.20260506084015-8bdbc27272c9 06 May 2026 none Apache-2.0 — Details →
v0.151.1-0.20260505235532-6ec45281c0e1 05 May 2026 none Apache-2.0 — Details →
v0.151.1-0.20260505073342-f980c16c5c64 05 May 2026 none Apache-2.0 — Details →
v0.151.1-0.20260504084219-cb864432e281 04 May 2026 none Apache-2.0 — Details →
v0.151.1-0.20260504072629-aa378cd980ba 04 May 2026 none Apache-2.0 — Details →
v0.151.1-0.20260501011435-655cd21d43a2 01 May 2026 none Apache-2.0 — Details →
v0.151.1-0.20260430073220-8dcaffe2f129 30 Apr 2026 none Apache-2.0 — Details →
v0.151.1-0.20260429041030-17b1988028e1 29 Apr 2026 none Apache-2.0 — Details →
v0.151.0 28 Apr 2026 none Apache-2.0 — Details →
v0.150.1-0.20260426122650-a96553be4513 26 Apr 2026 none Apache-2.0 — Details →
v0.150.1-0.20260424070108-a4fc560e731c 24 Apr 2026 none Apache-2.0 — Details →
v0.150.1-0.20260423062142-b34fd4d97a33 23 Apr 2026 none Apache-2.0 — Details →
v0.150.1-0.20260422055834-f2d13bcaa4c1 22 Apr 2026 none Apache-2.0 — Details →
v0.150.1-0.20260421042908-d38d1f997844 21 Apr 2026 none Apache-2.0 — Details →
v0.150.1-0.20260420055136-0004fc9303e2 20 Apr 2026 none Apache-2.0 — Details →
v0.150.1-0.20260417041256-c497d505f672 17 Apr 2026 none Apache-2.0 — Details →
v0.150.1-0.20260416181400-64681ae96929 16 Apr 2026 none Apache-2.0 — Details →
v0.150.0 13 Apr 2026 none Apache-2.0 — Details →
v0.149.1-0.20260410073551-5a67a110f773 10 Apr 2026 none Apache-2.0 — Details →
v0.149.1-0.20260409082430-6a09ff1a9204 09 Apr 2026 none Apache-2.0 — Details →
v0.149.1-0.20260409064153-628a3c6ac47e 09 Apr 2026 none Apache-2.0 — Details →
v0.149.1-0.20260408033340-69299e05ad32 08 Apr 2026 none Apache-2.0 — Details →
v0.149.1-0.20260407054623-d81b590c4c44 07 Apr 2026 none Apache-2.0 — Details →
v0.149.1-0.20260405114931-72df730a0e2c 05 Apr 2026 none Apache-2.0 — Details →
v0.149.1-0.20260403024604-b41f28058ad1 03 Apr 2026 none Apache-2.0 — Details →
v0.149.1-0.20260401220804-e71d093d76e8 01 Apr 2026 none Apache-2.0 — Details →
v0.149.1-0.20260401071500-f02c97a7d126 01 Apr 2026 none Apache-2.0 — Details →
v0.149.0 31 Mar 2026 none — — Details →
v0.148.1-0.20260326073602-3f35844b2cb9 26 Mar 2026 none — — Details →
v0.148.1-0.20260320061215-02f427266838 20 Mar 2026 none — — Details →
v0.148.1-0.20260319063015-7c92e4f06550 19 Mar 2026 none — — Details →
v0.148.1-0.20260318081204-2795bfda55a8 18 Mar 2026 none — — Details →
v0.148.1-0.20260318060332-f4c0a4ae513e 18 Mar 2026 none — — Details →
v0.148.0 17 Mar 2026 none — — Details →
v0.147.1-0.20260317070140-3b81fc256a5f 17 Mar 2026 none — — Details →
v0.147.1-0.20260316083615-42194051df3a 16 Mar 2026 none — — Details →
v0.147.1-0.20260315220410-cb1f1bb54ee8 15 Mar 2026 none — — Details →
v0.147.1-0.20260313015156-8e5e57fbe6b1 13 Mar 2026 none — — Details →
v0.147.1-0.20260312064502-df3a29411865 12 Mar 2026 none — — Details →
v0.147.1-0.20260311073248-f81930181215 11 Mar 2026 none — — Details →
v0.147.1-0.20260310052925-60ae1af2700c 10 Mar 2026 none — — Details →
v0.147.1-0.20260309082836-dc60d96a6045 09 Mar 2026 none — — Details →
v0.147.1-0.20260307015953-53ae84cdebae 07 Mar 2026 none — — Details →
v0.147.1-0.20260306045252-10f63383121c 06 Mar 2026 none — — Details →
v0.147.1-0.20260305080526-0cf514fa0ab3 05 Mar 2026 none — — Details →
v0.147.0 02 Mar 2026 none — — Details →
v0.146.1-0.20260225075228-26f5bf4ee689 25 Feb 2026 none — — Details →

The newest 120 of 1,444 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor

Is github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor safe to use?

Vulert has no vulnerabilities on record for github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor's Vulert package health score?

Vulert scores github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor 91/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor affected?

No. v0.163.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor have?

0 vulnerabilities are recorded for github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.