# Extend 'Expires On' date on a vulnerability exception

**URL:** <https://discuss.rapid7.com/t/extend-expires-on-date-on-a-vulnerability-exception/31502>\
**Category:** InsightVM\
**Tags:** vulnerability-management\
**Created:** [January 4, 2024, 8:37pm UTC](https://discuss.rapid7.com/t/extend-expires-on-date-on-a-vulnerability-exception/31502 "2024-01-04T20:37:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gnewman](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/g/50afbb/32.png) [@gnewman](https://discuss.rapid7.com/u/gnewman)\
**Post date:** [January 4, 2024, 8:37pm UTC](https://discuss.rapid7.com/t/extend-expires-on-date-on-a-vulnerability-exception/31502/1 "2024-01-04T20:37:37Z")

</div>

When we create a vulnerability exception, we put an **Expires On** date on it. The logic being we should periodically come back and review that exception and confirm it is still required, rather than leaving it in place for ever.

Is there a way to edit an exiting vulnerability exception to extend this date? Or do we have to recreate it completely with the new date?

---

<div class="post-metadata">

**Author:** ![Dave](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/d/ee7513/32.png) [@Dave](https://discuss.rapid7.com/u/Dave)\
**Post date:** [December 23, 2024, 9:50am UTC](https://discuss.rapid7.com/t/extend-expires-on-date-on-a-vulnerability-exception/31502/2 "2024-12-23T09:50:40Z")

</div>

This would be a great option. Today I had to delete an already existing exception to create a new one with an extended end date.

---

<div class="post-metadata">

**Author:** ![jkidd](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/j/a8b319/32.png) [@jkidd](https://discuss.rapid7.com/u/jkidd)\
**Post date:** [April 7, 2025, 5:43am UTC](https://discuss.rapid7.com/t/extend-expires-on-date-on-a-vulnerability-exception/31502/3 "2025-04-07T05:43:28Z")

</div>

Hi gnewman,

I have found you can “extend” the expiry date of a Vulnerability Exception using the Rapid7 InsightVM API. You’ll need to find the ID of the Vulnerability Exception and send a PUT request to [InsightVM API (v3)](https://help.rapid7.com/insightvm/en-us/api/index.html#operation/updateVulnerabilityExceptionExpiration) with the body containing the new date in the future:

 ![image](https://forum-uploads-hub-prod-1-us-east-1-rapid7-com.s3.dualstack.us-east-1.amazonaws.com/original/2X/f/faf0df6f2b42a6e325a641d77f4b629b9af79b44.png)

There doesn’t seem to be any functionality to do this in the InsightVM Security Console but it would be nice to have.