VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/peterzen/goresolver: vulnerability history, versions and safety

github.com/peterzen/goresolver is a package in the Go ecosystem. Vulert records 4 vulnerabilities for it across 9 releases, from Sep 2022 to Dec 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H2 U2
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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.

See all github.com/peterzen/goresolver vulnerabilities

Vulert verdict on github.com/peterzen/goresolver v1.2.0 i

Updated on 23 Oct 2026

Careful: v1.2.0 has 4 known vulnerabilities, and 4 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 55/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v1.2.0 — affected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 28 Dec 2022 i
  • Highest CVSS 7.7 i
  • With no published fix 4 i
  • Stars 25 i
  • OpenSSF scorecard 2/10 i
  • Last release 7 months ago i
  • Licence ISC 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/peterzen/goresolver, 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
v1.2.0 17 Mar 2026 H2 U2 ISC No Details →
v1.1.0 16 Feb 2026 H2 U2 ISC No Details →
v1.0.3-0.20250625235235-558865f5495d 25 Jun 2025 H2 U2 ISC No Details →
v1.0.3-0.20240102173207-b59372393acd 02 Jan 2024 H2 U2 ISC No Details →
v1.0.3-0.20200507002345-f5351f97ccb0 07 May 2020 H2 U2 ISC No Details →
v1.0.2 07 Jul 2019 H2 U2 ISC No Details →
v1.0.1 05 Mar 2019 H2 U2 ISC No Details →
v1.0.1-0.20190305222327-eb666061a80f 05 Mar 2019 H2 U2 ISC No Details →
v1.0.0 03 Mar 2019 H2 U2 ISC No Details →

All 9 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/peterzen/goresolver

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-3346: go-resolver - Attacker-controlled Domains Due to Unvalidated RRSIG RRs 7.7 high No fix published 28 Dec 2022
CVE-2022-3347: go-resolver's DNSSEC validation not performed correctly 7.7 high No fix published 28 Dec 2022
CVE-2022-3346: Incorrect DNSSEC validation in github.com/peterzen/goresolver N/A unrated No fix published 29 Sep 2022
CVE-2022-3347: Incorrect DNSSEC validation in github.com/peterzen/goresolver N/A unrated No fix published 29 Sep 2022

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/peterzen/goresolver

Is github.com/peterzen/goresolver safe to use?

Vulert records 4 vulnerabilities for github.com/peterzen/goresolver in Go: 0 critical, 2 high, 0 medium and 0 low, plus 2 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is github.com/peterzen/goresolver's Vulert package health score?

Vulert scores github.com/peterzen/goresolver 55/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/peterzen/goresolver affected?

Yes. v1.2.0, the version you would install today, has 4 known vulnerabilities, and 4 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/peterzen/goresolver should I use?

v1.2.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/peterzen/goresolver have?

4 vulnerabilities are recorded for github.com/peterzen/goresolver in the Go ecosystem: 0 critical, 2 high, 0 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/peterzen/goresolver vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/peterzen/goresolver in the last 12 months, and the oldest entry in this database dates to 29 Sep 2022. 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/peterzen/goresolver 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/peterzen/goresolver for upcoming vulnerabilities?

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