What is CVE-2026-62282?

CVE-2026-62282 is a medium-severity server-side request forgery (SSRF) vulnerability in opencve (pip), affecting versions <= 1.5.0. It is fixed in 3.0.0. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

How severe is CVE-2026-62282?

CVE-2026-62282 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of opencve are affected by CVE-2026-62282?

opencve (pip) versions <= 1.5.0 is affected.

Is there a fix for CVE-2026-62282?

Yes. CVE-2026-62282 is fixed in 3.0.0. Upgrade to this version or later.

Is CVE-2026-62282 exploitable, and should I be worried?

Whether CVE-2026-62282 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-62282 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-62282?

Upgrade opencve to 3.0.0 or later.

CVE-2026-62282 in opencve

Q: How severe is CVE-2026-62282?

CVE-2026-62282 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of opencve are affected by CVE-2026-62282?

opencve (pip) versions <= 1.5.0 is affected.

Q: Is there a fix for CVE-2026-62282?

Yes. CVE-2026-62282 is fixed in 3.0.0. Upgrade to this version or later.

Q: Is CVE-2026-62282 exploitable, and should I be worried?

Whether CVE-2026-62282 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-62282 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-62282?

Upgrade opencve to 3.0.0 or later.

Summary

OpenCVE: Server-Side Request Forgery (SSRF) in notifications

Workarounds

Users unable to upgrade should restrict outbound network access from OpenCVE to trusted external destinations using firewall rules, network policies, or egress filtering.

Where possible, access to localhost interfaces, private network ranges, and cloud metadata services should be blocked from the OpenCVE application environment.

Disabling access to the notification testing functionality also mitigates the issue.

Impact

OpenCVE contains a Server-Side Request Forgery (SSRF) vulnerability in the notification testing functionality for both Webhook and Slack integrations.

An authenticated user with permission to configure notification channels can trigger test requests to arbitrary HTTP(S) endpoints. Insufficient validation of target destinations allows requests to be sent to hosts reachable from the OpenCVE server, including internal network resources, localhost interfaces, and cloud metadata services.

Successful exploitation could allow an attacker to interact with internal services that are not otherwise accessible from the Internet and retrieve information from HTTP-based services reachable by the OpenCVE instance.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2026-62282 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.0.0); upgrading removes the vulnerable code path.

Affected versions

opencve (<= 1.5.0)

Security releases

opencve → 3.0.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The vulnerability has been fixed in OpenCVE version 3.0.0, users should upgrade to version 3.0.0 or later.

The fix introduces additional validation of user-supplied URLs used by the notification testing functionality and prevents requests to localhost, private network ranges, link-local addresses, cloud metadata services, and other non-public destinations.

Frequently Asked Questions

What is CVE-2026-62282? CVE-2026-62282 is a medium-severity server-side request forgery (SSRF) vulnerability in opencve (pip), affecting versions <= 1.5.0. It is fixed in 3.0.0. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
How severe is CVE-2026-62282? CVE-2026-62282 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of opencve are affected by CVE-2026-62282? opencve (pip) versions <= 1.5.0 is affected.
Is there a fix for CVE-2026-62282? Yes. CVE-2026-62282 is fixed in 3.0.0. Upgrade to this version or later.
Is CVE-2026-62282 exploitable, and should I be worried? Whether CVE-2026-62282 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-62282 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-62282? Upgrade opencve to 3.0.0 or later.