CVE-2026-58371
3.1 · LOWOverview
CVE-2026-58371 is a low-severity vulnerability. It was published on June 30, 2026 and has a CVSS 3.1 base score of 3.1 (LOW).
This vulnerability has a CVSS 3.1 base score of 3.1, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
Technical Description
SeaweedFS before 4.30 reflects the callback query parameter verbatim into responses served with Content-Type application/javascript in the shared writeJson helper (weed/server/common.go), with no callback-name validation, no X-Content-Type-Options: nosniff header, and no CORS allow-list. Every JSON endpoint that uses writeJson - including the unauthenticated master endpoints /dir/status, /dir/lookup and /cluster/status, the volume server /status, and the filer directory listing, all reachable in the default configuration (no -whiteList, no security.toml, bound to 0.0.0.0) - can therefore be loaded cross-origin via a script tag with a chosen callback, letting a third-party web page read cluster topology, volume server URLs and gRPC ports, file identifiers, and directory listings. Because the callback string is reflected at the start of the body and no nosniff header is sent, MIME-sniffing clients may also interpret the reflected content as HTML.
Remediation
Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
References
Frequently Asked Questions
What is CVE-2026-58371?
CVE-2026-58371 is a low-severity vulnerability. It was published on June 30, 2026 and has a CVSS 3.1 base score of 3.1 (LOW).
How severe is CVE-2026-58371?
This vulnerability has a CVSS 3.1 base score of 3.1, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
How do I fix or remediate CVE-2026-58371?
Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2026-58371?
CyberStrike's AI-powered security agents can automatically detect CVE-2026-58371 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related LOW CVEs from 2026
View all →Improper handling of values in the microcode flow for some Intel(R) Processor Family may allow an es
A flaw was found in libsoup, a library used by applications to send network requests. This vulnerabi
A flaw was found in libsoup. A remote attacker, by controlling the method parameter of the `soup_mes
A flaw was found in libsoup. An attacker controlling the value used to set the Content-Type header c
OpenSC is an open source smart card tools and middleware. Prior to version 0.27.0, feeding a crafted
OpenSC is an open source smart card tools and middleware. Prior to version 0.27.0, sc_compacttlv_fin
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and C
HCL BigFix Service Management (SM) is susceptible to a Root File System Not Mounted as Read-Only. An
FacturaScripts is an open source accounting and invoicing software. Versions 2025.7 and prior contai
An integer underflow in the volxlate function in Netatalk 3.0.0 through 4.4.2 allows a local privile
Capsule is a multi-tenancy and policy-based framework for Kubernetes. To defend against namespace hi
Improper input validation in Microsoft Azure Attestation service and Device Health Attestation Servi