{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-11362 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-11362 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-11362 is a critical vulnerability in BINARY DataDog::DogStatsd, published on 5 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-11362 and fix it if it is affected.\n\nWhat it is: CVE-2026-11362 is a critical vulnerability in BINARY DataDog::DogStatsd, published on 5 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-11362 in the wild and no public exploit code.\n\nAffected product: BINARY DataDog::DogStatsd. 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-11362/ (Markdown: https://insights.sbomify.com/CVE-2026-11362/index.md)","id":"CVE-2026-11362","markdown":"https://insights.sbomify.com/CVE-2026-11362/index.md","name":"CVE-2026-11362","record":{"aliases":["GHSA-37fh-f35c-r73m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl DataDog library","requires_auth":"none","summary":"Attackers can inject arbitrary metrics or tags into DataDog monitoring via unsanitized input in the Perl DogStatsd library.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"datadog\\","vendor":"binary"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","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":"DataDog::DogStatsd versions through 0.07 for Perl allow metric injections from event tags.\n\nDataDog::DogStatsd does not properly sanitise input, allowing metric injections of data from untrusted sources.\n\nThe format_event method (used by the event method) does not validate the content of the tags, which may contain commas (allowing tags to be injected) or newlines, pipes and colons that allow metric injections.  (There is an ineffective s/|//g to remove pipes, but because the pipe is not escaped, it is interpreted as a regular expression metacharacter and has no effect.)","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":"DataDog::DogStatsd versions through 0.07 for Perl allow metric injections from event tags","id":"CVE-2026-11362","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Ninja Forms \u003c= 3.14.6 - Authenticated (Administrator+) PHP Object Injection via Form Import","id":"CVE-2026-11363"},"packages":[],"prev":{"headline":"Formidable Forms \u003c 6.32.1 - Unauthenticated Payment Bypass via PayPal APPROVAL_PENDING Subscription Status","id":"CVE-2026-11361"},"products":["DataDog::DogStatsd"],"published":"2026-06-05","related":[{"cvss_score":9.1,"headline":"DataDog::DogStatsd versions through 0.07 for Perl allow metric injections","id":"CVE-2026-9270","kev_date_added":null,"published":"2026-06-05"}],"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":"total"},"state":"PUBLISHED","updated":"2026-06-08","vendors":["BINARY"]},"summary":"Attackers can inject arbitrary metrics or tags into DataDog monitoring via unsanitized input in the Perl DogStatsd library.","url":"https://insights.sbomify.com/CVE-2026-11362/"}