A "Dirty Read" occurs in database management when a transaction reads data that has been modified by another ongoing transaction but not yet committed. This means that the reading transaction may access uncommitted changes, which could later be rolled back, leading to inconsistencies. For example, if Transaction A updates a record but hasn't committed the change, and Transaction B reads that record, Transaction B is performing a dirty read. This can cause issues in applications where data accuracy is critical, as it relies on potentially unstable information from the database.