Clarification regarding the Modified Time update

[SURENKUMAR-0212]

Clarification Regarding the Modified Time Update on Advisory DLA-4353-1

We are currently syncing Debian data from the OSV all.zip dataset. While reviewing advisory DLA-4353-1, we observed a discrepancy in the modified timestamp.

• The modified time we recently received was: 2026-03-09T01:18:ssZ
• However, the actual modified timestamp in the advisory appears to be: 2025-10-29T12:17:36.531440Z

Initially, the timestamp matched the expected value. At some point in between, it appears the datetime changed, and it has now reverted back to the original value.

Could you please confirm whether any updates or changes were made to this advisory during that period which might have caused the modified timestamp to change?

Thank you for your help in clarifying this.

Note: We checked on our side and did not identify any issues in our processing or data handling.

[github-actions]

✨ Thank you for your interest in OSV.dev's data quality! ✨

Please review our FAQ entry on how to most efficiently have this addressed.

[another-rex]

Hello! Thanks for the detailed report.

This seems to be a bug with our recent rework of our pipeline, which I made a fix for going forward here: #5045, releasing early next week.

We'll also do a pass to revert the backward modification date changes on these records right after the release next week as well! Just note that this could potentially miss a few records between the snapshot we are using to do the revert (about 1 week old) and now, so a full resync on your end would be ideal.

I'll update and close this issue once we have released and updated the records :)

[SURENKUMAR-0212]

Thank you for the clarification and for working on the fix.

One additional question from our side: does OSV track the history of changes for a vulnerability record (for example, modification history or revision tracking)? If so, is that information available publicly, such as through the OSV GitHub repository or another source?

This would help us better understand and track updates to vulnerability records.