Every system accumulates technical debt. Some is deliberate, a shortcut taken to ship sooner. Some comes from requirements changing after the design was made, and some from dependencies aging. Like financial debt, a little can be useful, but unmanaged debt compounds.
Managing it means making debt visible, paying down the parts that slow important work or create risk, and avoiding new debt in critical areas such as security and data integrity. A short list of known debt, reviewed each quarter, is usually enough to keep it under control.