{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-50637 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-50637 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-50637 is a high-severity vulnerability in PEVANS Metrics::Any::Adapter::Statsd, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-50637 and fix it if it is affected.\n\nWhat it is: CVE-2026-50637 is a high-severity vulnerability in PEVANS Metrics::Any::Adapter::Statsd, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-50637 in the wild and no public exploit code.\n\nAffected product: PEVANS Metrics::Any::Adapter::Statsd. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-50637/ (Markdown: https://insights.sbomify.com/CVE-2026-50637/index.md)","id":"CVE-2026-50637","markdown":"https://insights.sbomify.com/CVE-2026-50637/index.md","name":"CVE-2026-50637","record":{"aliases":["GHSA-q83q-ghhm-p7g4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl Statsd adapter","requires_auth":"none","summary":"Attackers can inject arbitrary metrics into Statsd servers via unsanitized input in the Perl Metrics::Any::Adapter::Statsd library.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"metrics\\","vendor":"pevans"}],"cvss":{"score":8.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-93","name":"Improper Neutralization of CRLF Sequences"},{"id":"CWE-150","name":"Improper Neutralization of Escape, Meta, or Control Sequences"}],"description":"Metrics::Any::Adapter::Statsd versions before 0.04 for Perl does not protect against metric injections.\n\nThe statsd protocol (and extensions) allow mutiple metrics, separated by newlines, to be sent per packet.\n\nThe send method does not validate the contents of the metric names or values. If the names have newlines and statsd control characters (colon, pipe) then metric injections are possible.\n\nVersion 0.04 fixed this by modifying the _make method to block metric names with characters below ASCII 32 (which includes the newline), or colons or pipes.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Metrics::Any::Adapter::Statsd versions before 0.04 for Perl does not protect against metric injections","id":"CVE-2026-50637","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Metrics::Any::Adapter::DogStatsd versions before 0.04 for Perl does not protect against metric injections","id":"CVE-2026-50638"},"packages":[],"prev":{"headline":"LimeSurvey RemoteControl invite_participants/remind_participants SQL Injection","id":"CVE-2026-50636"},"products":["Metrics::Any::Adapter::Statsd"],"published":"2026-06-10","related":[{"cvss_score":9.1,"headline":"Metrics::Any::Adapter::DogStatsd versions before 0.04 for Perl does not protect against metric injections","id":"CVE-2026-50638","kev_date_added":null,"published":"2026-06-10"},{"cvss_score":6.5,"headline":"Metrics::Any::Adapter::SignalFx versions before 0.04 for Perl does not protect against metric injections","id":"CVE-2026-50639","kev_date_added":null,"published":"2026-06-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-19","vendors":["PEVANS"]},"summary":"Attackers can inject arbitrary metrics into Statsd servers via unsanitized input in the Perl Metrics::Any::Adapter::Statsd library.","url":"https://insights.sbomify.com/CVE-2026-50637/"}