{"version":"2.1.265","anchor":"urls-with-embedded-credentials-now-rejected","canonical_anchor":"urls-with-embedded-credentials-now-rejected","heading":"URLs with embedded credentials now rejected","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/urls-with-embedded-credentials-now-rejected","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### URLs with embedded credentials now rejected\n\nURLs containing a username or password, like user:pass@host, are now rejected during normalization\n\n**What**\n\nA URL-handling function that previously accepted any `http` or `https` URL now rejects URLs that embed a username or password, such as `user:pass@host`. Instead of processing the URL, it returns nothing.\n\n**Why**\n\nURLs with embedded credentials can leak sensitive information or be used to disguise the real destination of a link. Rejecting them closes off that risk.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}