Immediately fixing a vulnerability is not always optimal.
When you have a planned release in a few months that will naturally eliminate the vulnerability, such as a language version update or a library change,
fixing the vulnerability immediately, means your engineering team wastes time and effort. Additionally, fixing a vulnerability immediately can mean delaying important releases or missing critical deadlines.
Instead of pushing for an immediate hot patch, use
Raven’s Virtual patching to delay the fix and protect the application until the time is right.