<!-- canonical: https://0xsimao.com/findings/spectra-metavault-variable-shadowing-metavaults-registry -->

# Some variable shadowing in MetavaultsRegistry

Low/Info · Sherlock · Yield-tokenisation vaults · 16th December 2025

Finding I-3 of the Spectra MetaVault Bridge security review.

- Protocol: https://www.spectra.finance/
- Report: /reports/spectra-metavault-bridge
- Source: https://github.com/0xsimao/audits/blob/main/Sherlock/private-audits/2025-12-16-spectra-metavault.pdf

---

## Summary

`market` and `chainConfig` shadow the corresponding functions.

## Vulnerability Detail

Market and chainConfig are used throughout the contract as memory variable, but there already exist functions with these names.

## Impact

QA

## Code Snippet

For example, [market](https://github.com/sherlock-audit/2025-12-spectra-metavault-update-dec-16th/pull/2/files#diff-d6dbd850708b46c46f64d8bc2d13e4fe2de6f7ac75f0981bf638274c7830a293R148) and [market()](https://github.com/sherlock-audit/2025-12-spectra-metavault-update-dec-16th/pull/2/files#diff-d6dbd850708b46c46f64d8bc2d13e4fe2de6f7ac75f0981bf638274c7830a293R527).

## Tool Used

Manual Review

## Recommendation

Consider changing the variable or function names.

Disclosed by 0xSimao (https://0xsimao.com/).